The Contribution Process Overview

Developers, test/QA engineers, and other team stakeholders are considered Contributors. Contributors who may contribute source files (configuration files, source code C#, etc.) must create a Fork to manage their work in the environment.

1. Create a Fork (copy of the Shared Team Repository).
2. Clone the Fork to the local environment and check out the Branch to work on.
3. Add a Remote Reference to the Team Repo to fetch and rebase its current work.
4. Make changes in the Repository and test locally by running RunIntegrateTest, ContinuousIntegration, and other scripts.
5. Commit the changes locally and then push.
6. Create the Pull request.
7. Updates to the Source Branch after the Pull request is created and the initial creation triggers a ContinuousIntegrationPipeline based on Branch policy.
8. When the ContinuousIntegrationPipeline has successfully built the Artifact, it will run a test and report a green status or not. Based on that status, reviewers may approve the PR. They may also reject it, even with a green Build, if some other project practice is violated.
9. When the PR is approved and merged, the Branch typically has a policy of rerunning the ContinuousIntegrationPipeline. This ensures that all PRs are still in sync. The goal is to ensure that the Common RepoBranch is always buildable.