-
-
Notifications
You must be signed in to change notification settings - Fork 32
GitHub guidelines
Piper edited this page Oct 11, 2021
·
2 revisions
A collection of guidelines for the team to norm on, to improve overall development speed.
Currently, (as of October 2021) the team uses a staging branch ("develop") that is cut weekly to the main trunk. The rationale for this was to have a testing environment as more stability improvements were made to the platform. All new pull requests should be open into develop.
Naming doesn't matter too much. I pattern I use is fix/github-issue-number or feat/github-issue-number.