![]() ![]() In conclusion, this is the recap of how Using Git Flow with GitKraken and Azure DevOps. ![]() To keep things clean it is better to delete it also locally Notice also that feature branch was deleted from remote. We can also notice the Tasks and User Story being closed automaticallyįinally, we can visually see the merge happened in GitKraken Once Merge being completed the Pull Request will be set to completed The PR will now indicate that the changes will be merged into develop. If change is good then the reviewer can now resolve the comment The new commit will appear in the Pull Request timeline He can push his new changes and reply to the comment by tagging the reviewer for example. The developer will be notified about the comment and make the required changes or reply to the comment Now a comment is posted we can see on the PR timeline a policy that it doesn’t comply to rules of having all comments resolved ( I can approve my own pull request but it is for this tutorial purpose)Ĭongratulations! Your environment is now ready to use and setup correctly.Ī nice feature is the fact that comments can be rich and including many formatting/tagging/images/Pull Request or items reference and much more.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |