After you've done the development work to fix a bug or remove a feature, you may want to contribute that code back to the Ed-Fi Core. (See the Code Submissions from Ed-Fi Licensees page for an overview of the development process.) This guide assumes you have already committed and pushed your changes to a Git repository.
Once all changes are committed, you may contribute the changes back to the Ed-Fi Alliance for inclusion in core using a pull request. The Alliance hosts the following repositories:
Click on the repository that contains your change.
Switch the "branch" dropdown to your development branch (e.g., feature-JIRAIssue-89).
Click New pull request.
Click the "Edit" button at the top of the pull request screen.
Make sure the "Base Fork" is "Ed-Fi-Alliance\Ed-Fi-Dashboard" (or appropiate repository) and "base" is set to the development branch.
GitHub should calculate the pull request at this point and you should see a green message saying it is ready to be automatically merged.
If you do not see this, then your forked code is out of date with the Ed-Fi Alliance code base. In this case, you must first pull the latest code and handle any merge conflicts prior to submitting a pull request.