You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After doing lots of work in the hub I have realised that we should start closing issues earlier than our current process so that we can display progress easily.
I suggest the following process:
Create a feature branch for your work
Make code and commit
Create a Pull Request to Develop
Code Check the Code and merge into Develop
Delete the Feature Branch
Close the Issue
This works only if I also ensure the following rules apply:
All issues are allocated into a Milestone
Milestones reflect all work that is carried out in a Release
If an Issue is closed without code, then the Milestone is removed
So when testing, we can see the contents of a release by checking the Closed issues from that Milestone.
I will update the documentation to reflect this.
The text was updated successfully, but these errors were encountered:
After doing lots of work in the hub I have realised that we should start closing issues earlier than our current process so that we can display progress easily.
I suggest the following process:
This works only if I also ensure the following rules apply:
So when testing, we can see the contents of a release by checking the Closed issues from that Milestone.
I will update the documentation to reflect this.
The text was updated successfully, but these errors were encountered: