π―π΅ ζ₯ζ¬θͺηγ―γγ‘γ ο½ π¨π³ δΈζηε¨ζ€
| Branch Name | Role |
|---|---|
main |
For releases and backups (do not touch directly) |
develop |
For integration (do not push directly) |
[name] |
Personal branch for each student (managed remotely) |
[name]_[feature] |
Feature development branch |
Examples:
| Branch Name | Description |
|---|---|
mtanaka |
Tanaka's personal branch |
mtanaka_unet |
Tanaka's UNet development branch |
Warning
Do NOT push directly to the develop branch!
- Create the remote
[name]branch - Pull from
developinto the remote[name]branch to keep it up to date - Pull the remote
[name]branch to the local[name]branch - Push the local
[name]branch to the remote[name]branch - Create a Pull Request from the remote
[name]branch todevelop
How you develop on the local [name] branch is up to you.
- Create the
mainbranch - Create the
developbranch frommain - Set
developas the default branch
- Create a
[name]branch (remote) fromdevelop - Clone only the
[name]branch (remote)
e.g.) [name] | mtanaka
git clone -b [name] --single-branch git@github.com:visionimageprocessing/welcome.git- Pull from
developinto the remote[name]branch to keep it up to date - Pull the remote
[name]branch to the local[name]branch - Create a local
[name]_[feature]branch from the local[name]branch - Develop on the local
[name]_[feature]branch
- Merge the local
[name]_[feature]branch into the local[name]branch - Push the local
[name]branch to the remote[name]branch - Delete the local
[name]_[feature]branch
- Create a Pull Request from the remote
[name]branch todevelop - The repository administrator reviews and merges the Pull Request
Warning
Do NOT push directly to the develop branch!