Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change in Github Process #481

Closed
adriancollier opened this issue Mar 25, 2014 · 1 comment
Closed

Change in Github Process #481

adriancollier opened this issue Mar 25, 2014 · 1 comment
Assignees

Comments

@adriancollier
Copy link
Contributor

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.

@adriancollier
Copy link
Contributor Author

Code is reviewed and merged.

@MichaelAkvo MichaelAkvo moved this to Done in RSR Dec 8, 2022
@MichaelAkvo MichaelAkvo added this to RSR Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant