Skip to content

Propose: Add PR timing guidance to version control standard #91

@virtualian

Description

@virtualian

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

  1. CI runs immediately - catch issues early
  2. Team visibility - others see work in progress
  3. Workflow integration - bots can comment (preview URLs, coverage reports, etc.)
  4. Better PR descriptions - written while context is fresh, not rushed at the end

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions