US079 - As a Developer I would like to use Git Branching for Bug Fixing so I can collaborate with proper coordination
Description:
As a developer, I want to use Git branching strategies for bug fixing, so that I can work in parallel with other team members, avoid merge conflicts, and maintain a clean and traceable codebase.
Linked Requirements & Use Cases:
Current Definition of Done
-
Git branching strategy is defined and documented -
Developers use branch naming convention tied to issue IDs -
Merge requests (MRs) are created per branch and reviewed -
Each bug fix is linked to an issue tracker entry via commit message -
Branch passes all CI checks before merge -
Documentation is updated with branching strategy examples
Acceptance Criterias
-
Developers can create dedicated branches for each bug fix -
Branches follow a naming pattern: e.g., bugfix/US079-issue-title -
Commits within the branch reference the related issue ID -
MRs trigger CI pipelines and automated tests -
MRs require code review before merging to main or release -
All merged branches are automatically deleted unless otherwise tagged -
Documentation for team branching workflow is available and shared
Edited by AH0987