Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Branch Name Validation #17

Closed
Sddilora opened this issue Apr 16, 2024 · 0 comments
Closed

Implement Branch Name Validation #17

Sddilora opened this issue Apr 16, 2024 · 0 comments
Assignees
Labels
automation Tasks related to automation or process optimization Be cross-team Collaboration required between teams medium priority Important issues to be addressed soon sub-issue Sub-task within a larger task

Comments

@Sddilora
Copy link
Member

This issue aims to implement a CI/CD process to validate branch names according to the established naming conventions. Branch names should follow a specific pattern or format to ensure consistency and clarity across the repository. This process will help maintain a clean and organized codebase by enforcing naming conventions for branches.

Branch Name Standardization

@Sddilora Sddilora added sub-issue Sub-task within a larger task automation Tasks related to automation or process optimization labels Apr 16, 2024
@Sddilora Sddilora added the medium priority Important issues to be addressed soon label Apr 16, 2024
@Sddilora Sddilora assigned SoyluAlaattin and unassigned Smnrgcl May 1, 2024
@Sddilora Sddilora added the cross-team Collaboration required between teams label May 1, 2024
@Sddilora Sddilora closed this as not planned Won't fix, can't repro, duplicate, stale May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Tasks related to automation or process optimization Be cross-team Collaboration required between teams medium priority Important issues to be addressed soon sub-issue Sub-task within a larger task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants