finishing-a-development-branch

Topics in the source

• Finishing a Development Branch

Confirm the final change has completed the project's independent quality-check and required checks. Evidence must describe the current tree: rerun affected verification after material edits or integration changes, and report unresolved failures. Do not add another whole-branch review or repeat an unchanged successful test suite merely to follow this skill. Determine the repository, branch, base, worktree ownership, and uncommitted changes with read-only Git commands. Verify the intended target from the plan, upstream, or conversation before integrating. Follow the integration action already authorized by the user. The design approval already covers commits, feature-branch pushes, creating the PR and the merge. First, if the project's rules require the user's approval for the merge, or the merge automatically releases, publishes or deploys to production - an environment that customers or users rely on (exception X2; an automatic deploy to an environment for checking behavior (such as staging) that does not touch production - the production database, live payments, or sending to real customers and the like - is not X2; judge by the effect on customers or users, not by the name) - fin

This is an excerpt. Refer to the complete source and its current requirements.