Proposal
Add a "Pull Request Timing" section to the version control standard specifying when PRs should be created.
Problem
The current standard has:
- "Before Creating PR" checklist
- "PR Checklist"
- "Before Merging" checklist
But no guidance on when to create the PR in the development workflow.
Proposed Addition
## Pull Request Timing
**Create a draft PR immediately after the first push of a feature branch.**
**Rationale:**
- Enables CI checks from first commit
- Provides visibility into work in progress
- Allows automated workflows to comment (e.g., preview URLs)
- PR description written while context is fresh
Convert to ready-for-review when work is complete.
Context
Discovered while implementing GitHub Actions deployment workflows. The preview deployment workflow comments preview URLs on PRs, but this only works if a PR exists. Creating draft PRs early solves this and provides other benefits.
Benefits of Early Draft PRs
- CI runs immediately - catch issues early
- Team visibility - others see work in progress
- Workflow integration - bots can comment (preview URLs, coverage reports, etc.)
- Better PR descriptions - written while context is fresh, not rushed at the end
Proposal
Add a "Pull Request Timing" section to the version control standard specifying when PRs should be created.
Problem
The current standard has:
But no guidance on when to create the PR in the development workflow.
Proposed Addition
Context
Discovered while implementing GitHub Actions deployment workflows. The preview deployment workflow comments preview URLs on PRs, but this only works if a PR exists. Creating draft PRs early solves this and provides other benefits.
Benefits of Early Draft PRs