- Make sure that there is a corresponding issue for your change first. If there is none, create one.
- Create a fork in GitHub
- Create a branch off the
masterbranch. Name it something that that makes sense, such asissue-123orgithubhandle-issue. This makes it easy for everyone to figure out what the branch is used for. It also makes it easier to isolate your change from incoming changes from the origin. - Commit your changes and push your changes to GitHub.
- Create a pull request against the origin's
masterbranch. See How to: Submit a Pull Request.
...
Don't feel obliged to match every issue with a Pull Request. Simply filing issues for problems you encounter is a great way to contribute too!
| Tip |
|---|
We use JIRA to keep track of issues, see Ed-Fi Issue Tracker. Keep in mind that some tech components require a license, for access level check out our Technical Community Guidelines. |
...
- DO NOT submit Pull Requests that alter licensing related files or headers. If you believe there's a problem with them, file an issue and let us take care of it.
...
| Note |
|---|
We borrowed these awesome guidelines from the .NET CoreFX team https://github.com/dotnet/corefx/wiki/Contributing |
...