This repository was archived by the owner on Feb 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Git Development Workflow
Anurag Pratik edited this page Aug 9, 2017
·
1 revision
Here is what your workflow will look like.
- Git clone the repository (
git clone https://github.com/AzureAD/rms-sdk-for-cpp.git) - Checkout the dev branch (
git checkout dev) - Fork off a feature/fix branch off dev (
git checkout -b feature/the-deathly-hallows) - Do your changes. Push your local branch to remote if you want to use repository's continuous integration capabilities (
git push -u origin feature/the-deathly-hallows). MSFT employees can access all CI capabilities by clicking on the "red cross" or "green checkmark" icon beside any commit and then clicking on the "Details" link. On the page that follows, you can "Queue New Build" for the feature branch you are developing in. - Get your code reviewed while developing on the feature branch.
- Stash changes and write a neat commit message when ready to merge changes to dev.
- Create a pull request to merge changes to dev. This will run continuous integration tests to check for regressions in the merge. Once CI runs are green, merge pull request and delete the feature branch.
Refer to the Git Cheat Sheet for best practices on branching strategies, commit messages and useful Git commands.