From edf2b5c2b9f28471b118512fe9d5a196883b9910 Mon Sep 17 00:00:00 2001 From: Le Hoang Nam Date: Thu, 10 Apr 2025 14:59:28 +0700 Subject: [PATCH] Fix terminology for repository and branch permissions in GitFlow documentation --- gitflow-workflow.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/gitflow-workflow.md b/gitflow-workflow.md index dfa082d..6dec396 100644 --- a/gitflow-workflow.md +++ b/gitflow-workflow.md @@ -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)