MERGE GYMLEADERSHIP FIELD GUIDE
TAKE-TO-WORK REFERENCE · v1.0
The GitHub leader's
field guide.
Use this when the course is over and a real decision is in front of you. It is designed for the person accountable for clarity, risk, and flow—not just the person writing code.
01
BEFORE YOU APPROVE
Eight questions that slow down risk—not delivery.
- 01
What problem does this pull request solve?
- 02
Is the scope small enough to understand and reverse?
- 03
Does the diff match the stated outcome?
- 04
Are security, privacy, money, or customer risks visible?
- 05
What evidence shows the change works?
- 06
Are required checks green—and do I know what they cover?
- 07
Are blocking comments resolved by the right owner?
- 08
Is the team prepared to observe and reverse the change?
02
MAKE THE REVIEW STATE MEAN SOMETHING
Comment, approve, or request changes?
DecisionUse it whenYour standard
CommentYou have useful context or a questionThe PR can proceed while the discussion continues
ApproveYou reviewed your area and believe it is readyYou are comfortable with this change reaching main
Request changesA concrete risk must be addressedName the blocker and the safe outcome—not the person
03
STOP-THE-MERGE SIGNALS
Six red flags worth your attention.
Exposed secret
Rotate or revoke it first. Deleting the line does not un-leak history.
Failed or missing checks
Understand the failure or missing evidence before considering merge.
Huge mixed-purpose diff
Ask for smaller PRs so each decision is understandable and reversible.
Direct change to main
Confirm this is intentional and governed; normal work belongs on a branch.
Unresolved business question
Automation cannot decide product intent. Get the accountable owner.
Pressure to bypass rules
Urgency raises the need for explicit risk ownership; it does not erase it.
04
FROM VAGUE TO TRACEABLE
Translate team shorthand into a useful question.
WHEN YOU HEAR“It’s in GitHub.”
→ASKWhich repository, issue, or pull request should I inspect?
WHEN YOU HEAR“The PR is green.”
→ASKWhich checks passed, and what important risk is outside their coverage?
WHEN YOU HEAR“It’s just a small change.”
→ASKCan the diff and rollback plan confirm that?
WHEN YOU HEAR“There’s a conflict.”
→ASKWhich intended behavior should survive, and who owns that decision?
WHEN YOU HEAR“We can fix it forward.”
→ASKWhat is the customer impact while we do, and can we reverse safely?
05
THE FIRST WEEK
Turn fluency into operating rhythm.
Find unowned work, unclear outcomes, and items blocked without a decision owner.
Watch aging PRs, failed checks, unresolved reviews, and work drifting from main.
Make risk, evidence, and reversibility explicit while the change is still cheap.
Turn a repeated reminder into a template, required check, owner, or repository rule.
06
PLAIN-ENGLISH GLOSSARY
The terms worth keeping close.
- Git
- The version-control system that records changes.
- GitHub
- The collaboration platform built around Git repositories.
- Repository
- A project and its complete change history—often shortened to repo.
- README
- The project’s front page and operating guide.
- Commit
- An intentional saved checkpoint with a message and author.
- Actions
- Automated workflows such as tests, checks, and deployments.
- Diff
- The exact additions and removals between two versions.
- Commit message
- A concise explanation of the change captured by a commit.
- .gitignore
- Rules that keep local or sensitive files from being tracked.
- Branch
- An independent line of changes within a repository.
- main
- The conventional name for the repository’s default, official branch.
- Checkout / switch
- Move your working view from one branch to another.
- Pull request (PR)
- A request to review and merge changes from one branch into another.
- Base branch
- The branch that will receive the proposed changes.
- Compare branch
- The branch containing the proposed changes.
- Review
- Structured feedback and a decision on a pull request.
- Merge conflict
- Competing changes Git cannot safely combine without a human decision.
- Branch protection
- Rules that can require reviews, checks, or other conditions before merge.
- Issue
- A trackable unit for a bug, task, idea, or decision.
- Assignee
- The person currently responsible for moving an item forward.
- Project
- A configurable planning view across issues, PRs, and draft ideas.
- Workflow
- An automated process defined in the repository and triggered by an event.
- Required check
- An automated result that must pass before a protected branch can be updated.
- Secret
- A credential such as a token or key that must never be committed to repository history.