managing-git-workflow

Branch naming in HASH git workflow follows the format `<shortname>/h-XXXX-description`, where h-XXXX references your Linear ticket. This convention ensures traceability between branches, commits, and issue tracking, so all work is linked to the original task.

Pull requests use a standard template that captures context and changes clearly. The template guides PR title formatting and description structure to ensure reviewers understand the work, dependencies are documented, and the change connects back to the Linear ticket via your branch name.

Code reviews follow a checklist covering diff verification, testing, and compliance with branch and commit standards. The workflow guides you through checking changes against PR requirements and Linear ticket scope to maintain consistency across feature work, bug fixes, and ticket-driven tasks.

Yes. The workflow applies to feature work, bug fixes, and Linear-ticket-driven tasks. Branch naming, PR templates, and review checklists enforce the same format and rigor across all work types, ensuring consistent traceability regardless of task category.

The workflow includes quick reference commands for PR exploration, branch creation, and commit management. These commands streamline checking PR status, viewing diffs, and verifying branch names match the Linear ticket format before opening or reviewing.

Branch naming conventions that reference Linear tickets create a traceable link from code to issue tracking, making it easy to find related work, understand context during reviews, and maintain audit trails. This prevents confusion in teams and ensures accountability across development.