Branches: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 37: | Line 37: | ||
<pre> |
<pre> |
||
git checkout develop |
git checkout develop |
||
</pre> |
|||
===2.1 commit code=== |
|||
<pre> |
<pre> |
||
git add . |
|||
git commit -m <commit message> |
|||
</pre> |
|||
===2.2 upload commit to server=== |
|||
<pre> |
|||
git push |
|||
</pre> |
|||
Revision as of 01:57, 9 February 2024
Git branch model
- develop
- feature
- release
- master
Some basic rules for successful development using branches:
- master only gets updated from release
- develop is the main working branch
- develop is the source for new releases and features
- features can only go back into develop
resource: https://nvie.com/posts/a-successful-git-branching-model/
1. create a new development branch from master
git branch develop
2. develop code
git checkout develop
2.1 commit code
git add . git commit -m <commit message>
2.2 upload commit to server
git push