-
Notifications
You must be signed in to change notification settings - Fork 2
Branch Management
Maurits Kok edited this page Apr 28, 2021
·
4 revisions
Branch management is an important consideration for working collaboratively with git and GitHub. Branching allows you to diverge from the main line of development and continue to do work without messing with that main line [1]. A good method for branch management is Gitflow [2]. The referenced article contains all information.
Aim: implement new features into the code and release a new version.
- Development of the code takes place on the development (or dev) branch. When you want to work on a new feature or fix a bug, create a new feature branch from the development branch.
- Work on the code on the feature branch
- Create a pull request on GitHub to merge the feature branch into the development branch.
- Repeat previous steps to implement more features. Best practice is to keep the pull request small; this makes it easy to review and limits the possibilty of generating conflicts.
- When ready make a new release, create a release branch from the development branch.
- On the release branch: compile and package the software, update documentation.
- Create pull request to merge the release branch with the main branch. Delete release branch after merge.
![git-model](https://user-images.githubusercontent.com/15414938/110449882-f0639180-80c2-11eb-93a1-2688824c22cc.png)
[1] https://www.atlassian.com/git/tutorials/using-branches
[2] https://nvie.com/posts/a-successful-git-branching-model/
Project details
FAIR
MATLAB
- Code Structure
- Use Cases
- Project Data
- Variable Names
- GUI Architecture
- Packaging and Compiling
- Testing
Git and GitHub