-
Notifications
You must be signed in to change notification settings - Fork 0
Issue and Branch Conventions
Nick Piazza edited this page Jan 1, 2018
·
1 revision
The master branch is supposed to be a clean branch that is consistent with the current release. In the early stages, this may not be correct, but that will be the policy after the first release. The dev branch is where all work will be branched from.
All work must have an Issue created and assigned to a milestone. Each Issue will have an appropriate name and scope. Each Branch will be forked from dev and will be named with the following format.
<Issue Number>-<Issue Title>
An example branch name would be
3-Add HTTP/S check
The following Issue and Branch are compliant with this policy.