Git Branching & Release Workflow

Last Audited: 2026-08-14
Tier-2 Authoritative
In Plain Language

Our Git workflow enables continuous integration through trunk-based development with short-lived feature branches (<48 hours). By adopting the Conventional Commits standard (feat, fix, docs, refactor) and requiring GPG-signed commits, we maintain a clear, automated changelog and an immutable audit trail for regulatory compliance.

Trunk-Based Development & Short-Lived Branches

Long-lived branches create merge hell and obscure regression origins. We practice trunk-based development: all engineers branch off main (trunk), make small, focused changes, and merge back within 24 to 48 hours via audited pull requests.

Branch Naming Format

feature/NUP-101-language-tabs
fix/NUP-102-null-pointer-bug
docs/NUP-103-ieee-standards

PR Size Guidelines

Aim for ≤ 400 lines of modified code per PR. Smaller pull requests are reviewed 3x faster with 50% fewer escaped defects.

Conventional Commits Specification

Commit messages must follow the Conventional Commits v1.0.0 specification to automate semantic versioning and release notes:

feat(enablement): add 12-language selector to coding standards (NUP-101)
fix(auth): sanitize redirect parameter to prevent open redirect vulnerability (NUP-102)
docs(templates): author master software test plan boilerplate (NUP-103)
refactor(database): optimize composite index on patient vital readings (NUP-104)
test(security): add automated SAST scan verification unit test suite (NUP-105)

Branch Protection & GPG Non-Repudiation

  • Direct Push Disabled: The main branch is locked against direct pushes and force pushes.
  • Required Status Checks: All CI build, linting, and unit test suites must pass before merge button is enabled.
  • Signed Commits: Per FDA 21 CFR Part 11 and SOX ITGC controls, developers must sign commits with a verified GPG key to establish non-repudiation.
Try This with AI: Conventional Commit & PR Summary Author

Copy this prompt into your AI coding assistant to author clean commit messages.

Given the following git diff, generate a Conventional Commit message adhering to the feat/fix/docs format and write a 3-bullet PR summary explaining the rationale, risk impact, and verification steps.

Community Discussion & Feedback

Attributed peer feedback and official Netspective architecture notes.

Was this documentation helpful?(100% found this helpful • 0 ratings)

Leave Feedback or Question

○ Loading user info...
0/2000 chars

Discussion (0)

Loading discussion thread...