generated from chingu-voyages/voyage-template
-
Notifications
You must be signed in to change notification settings - Fork 3
Work Flow
Mikey Nichols edited this page Jan 17, 2024
·
8 revisions
- Team holds discussion about opportunities for improvement.
- Product Owner opens issue and creates a branch to house proposed changes. (i.e
47/task/add-checkbox) - Developer checks out this branch locally and then proceeds to create their own branch. (i.e
47/feature/checkbox/mnichols08) - Developer writes code to solve the issue and afterwards pushes the code to GitHub.
- Developer makes a pull request to merge their new branch with the one created by Product Owner.
- Product Owner reviews and approves or requests changes.
- Other developers have opportunity to modify code for a short time.
- Code is created initially inside of a
Secondary Branchwhich is then merged into it'sPrimary Branchand then intoalpha, thenbetafirst for testing, then once testing is complete a Pull Request is made into thedevelopmentbranch.
We still have not closed the Discussion for the Branch Naming Convention. It behooves you to play around with these in Git to form an opinion about them.