GIT doesn't enforce naming rules for branches and TAGs. This is a problem for standardization and "continous integration" when every repository has own naming.
Change request:
Add 2 new attributes to the repository settings:
1) branch naming pattern
This is a regular expression which shall match new branch names.
If the new branch name doesn't match the pattern, the system shall deny the commit.
2) Tag naming pattern
This is a regular expression which shall match new TAGs.
If the new TAG name doesn't match the pattern, the system shall deny the commit.
Example for pattern:
"check lowercase" = ~ /\L\w.*\E/
"complex project dependent pattern" = ~ /\L[release|hotfix|change|dev|ci|arch]\/DAS_FILA02_?[\d{3}]?[_\d{3}]?[\w.*]\E/
Benefit:
- repositories have branches and TAGs conform to the defined process
- users understand meaning of branches and TAGs and have it documented in the development process documentation
- Continuous Integration process may behave different for different branch and TAG names
by: Rudolf W. | over a year ago | SCM
Comments
Rudolf, this request is now available in TeamForge 21.0. Please refer to the following for more details: https://docs.collab.net/teamforge210/index.html#branch-and-tag-naming-conventions