Plane Tickets That Match Git Branches (PORT-N)
In fast-moving software development, orphan git branches and orphan issue tickets are two sides of the same operational breakdown. An engineer writes code in a branch called `fix-button` with no ticket reference, while a project board contains tickets marked In Progress that were abandoned weeks ago. Six months later, nobody can explain why a specific architecture decision was made or which business requirement prompted it.
To establish total traceability across my self-hosted platform, I enforce the PORT-N convention. Every non-trivial engineering task begins with an issue on our self-hosted Plane instance, which directly dictates branch naming, commit messages, pull requests, and automated Woodpecker CI feedback loops.
The lifecycle begins in Plane, where every work item is assigned a deterministic sequential identifier (e.g. `PORT-42`). The git branch created in Forgejo must strictly follow the format `feature/PORT-42-short-description` or `fix/PORT-42-short-description`. Branch names lacking the project prefix are rejected by pre-commit hooks and CI lint gates.