fix(*): update branch content with develop's changes

.github/workflows/check_branch.yml

@@ -12,8 +12,8 @@ jobs:
         steps:
             - uses: deepakputhraya/action-branch-name@master
               with:
-                  regex: '([a-z])+\/([a-z_-])+\/([a-z_-])+'
+                  regex: '([a-z])+\/([\dA-Za-z_-])+\/([\dA-Za-z_-])+\/([\dA-Za-z_-])+'
                   allowed_prefixes: 'feature,stable,fix,chore,docs,feat,build,ci,test,refactor,perf'
                   ignore: main,stage,develop
                   min_length: 4
-                  max_length: 120
+                  max_length: 150

documentation/branch-strategy.md

@@ -19,10 +19,11 @@ Our branch naming strategy follows a specific format and uses prefixes to
 indicate the purpose of the branch. The naming convention is structured as
 follows:
 
-- **Format**: `prefix/name/description`
-  - **prefix**: Indicates the type of work being done.
-  - **name**: Provides the last name of the developer in charge of the ticket.
-  - **description**: A brief description of the branch's purpose.
+- Format: `prefix/taskId/username/taskName`
+  - `prefix`: Indicates the type of work (e.g., feature, fix, chore).
+  - `taskId`: The task ID or ticket number associated with the branch.
+  - `username`: The developer's username or last name.
+  - `taskName`: The task or feature name.
 
 ### Allowed Prefixes
 
@@ -54,7 +55,7 @@ to follow the naming rules:
 Branch names must adhere to the following length constraints:
 
 - **Minimum Length**: 4 characters
-- **Maximum Length**: 120 characters
+- **Maximum Length**: 150 characters
 
 By following this branch naming strategy, we ensure clarity and consistency in
 our workflow, making it easier to understand the purpose and context of each

documentation/git-workflow.md

@@ -18,10 +18,11 @@ overview of our Git Flow:
 
 ## Branch Strategy
 
-- Format: `prefix/name/description`
+- Format: `prefix/taskId/username/taskName`
   - `prefix`: Indicates the type of work (e.g., feature, fix, chore).
-  - `name`: The last name of the developer in charge of the ticket.
-  - `description`: Brief description of the branch's purpose.
+  - `taskId`: The task ID or ticket number associated with the branch.
+  - `username`: The developer's username or last name.
+  - `taskName`: The task or feature name.
 - Allowed prefixes include: feature, stable, fix, chore, docs, feat, build, ci,
   test, refactor, perf.