dev-public/doc-gitflow-workflow
18
0
Fork 0
Code Issues Pull Requests Projects Activity

Fix terminology for repository and branch permissions in GitFlow documentation

Browse Source
This commit is contained in:
Le Hoang Nam 2025-04-10 14:59:28 +07:00
parent d0c9caafde
commit edf2b5c2b9
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
gitflow-workflow.md
View File

@ -15,8 +15,8 @@ GitFlow is a branching model for Git that helps teams manage feature development
## Repository Permissions:
✅ Only the HoD and Leaders can create, modify, and delete repository.\
✅ Only the HoD and Leaders and Leaders can change settings for repository.
✅ Only the HoD and Team Leaders can create, modify, and delete repository.\
✅ Only the HoD and Team Leaders can change settings for repository.
## Branch Permissions
@ -25,14 +25,14 @@ GitFlow is a branching model for Git that helps teams manage feature development
- Prevent rewriting history.
- Prevent branch deletion.
- Prevent changes without a pull request.
- Limit write access to Leaders.
- Limit write access to Team Leaders.
### ✅ `develop` branch: development branch
- Prevent rewriting history.
- Prevent branch deletion.
- Prevent changes without a pull request.
- Limit write access to Game leaders.
- Limit write access to Team Leaders.
### ✅ Other branches
@ -61,7 +61,7 @@ Gitflow is really just an abstract idea of a Git workflow. This means it dictate
The `master` branch contains the latest updates for the project currently running in the LIVE environment.
Any changes to the `master` branch must be performed through a pull request. Leaders will review and merge the changes accordingly.
Any changes to the `master` branch must be performed through a pull request. Team Leaders will review and merge the changes accordingly.
![GitFlow Timeline](images/gitflow-workflow/master-branch-diagram.png)
## 2️⃣ Develop Branch
@ -70,7 +70,7 @@ Develop branch contains the complete history of the project and serves as an int
We will create the SAT (Site Acceptance Test) version on the `develop` branch and tag it with an updated version number. Once approved and deployed to LIVE, we will merge this confirmed version into the `master` branch.
Any changes for the `develop` branch must be performed through pull request. Leaders will review and merge the changes accordingly.
Any changes for the `develop` branch must be performed through pull request. Team Leaders will review and merge the changes accordingly.
![GitFlow Timeline](images/gitflow-workflow/develop-branch-diagram.png)