feature-ship

Triage feature branch findings by evaluating reported issues against the slice's definition of done, classifying them as fix-now blockers or backlog items. This separation ensures only release-ready work is prepared for the final ship gate.

Preserve deferred backlog items by moving still-relevant findings into a durable backlog before closing the GitHub feature issue. This prevents losing track of future work during the final squash merge and workspace cleanup process.

The best way to ship a completed feature slice is executing a controlled squash merge to main. This collapses branch commits into a single release, closes the associated GitHub issue, and cleans up the local workspace.

Yes, releasing a branch requires git, GitHub issue handling, and the repo's prescribed scripted squash-merge workflow. It applies specifically to issue-driven feature work needing controlled release to main.

You should not use a squash merge for feature branch release when you need to preserve individual commit history for audit or compliance. Squash merging collapses all branch commits into a single commit on main during the cleanup process.