Page History
...
| Tip |
|---|
Agree upon a naming convention for branches. Examples: release or application version for release branches or ticket/user story number for feature branches. |
Registering & managing changes
After implementing a new feature it is time to register what you have changed and why these changes were donemade. This information can be described in the registration message. Often this is a combination of a ticket/user story number (reference to an issue tracking system) and a short description of the change.
...
...
| Tip |
|---|
Keep branches short-lived and the number of active branches limited to a minimum to prevent conflicts.Versions will be easier to manage and maintain and merging will be more fun without conflicts! |
...
Overview
Content Tools