Skip to content

Docs and changeset base branch guidance are inconsistent #350

New issue
New issue
Closed
Closed
Docs and changeset base branch guidance are inconsistent#350
Assignees
bradygaster
Labels
go:needs-researchNeeds investigationpriority:p1This sprintsquadSquad triage inbox — Lead will assign to a memberstatus:contributor-invitedA specific contributor has been invited to work on thistype:docsDocumentation work

Description

@matthewcorven
matthewcorven
opened on Mar 11, 2026

Summary

CONTRIBUTING.md tells contributors from forks to target dev, but .changeset/config.json still declares main as the base branch.

Why this matters

This creates conflicting contributor guidance:

  • PR workflow says to branch from and target dev
  • Changesets are configured against main

That mismatch makes it unclear which branch is authoritative for docs-only and package-impacting changes, and it increases the chance of malformed PRs or confusing changeset behavior.

Current references

  • CONTRIBUTING.md: PRs from forks must target dev
  • .changeset/config.json: "baseBranch": "main"

Suggested resolution

Pick one canonical contribution base branch and align:

  • CONTRIBUTING.md
  • .changeset/config.json
  • any CI or release docs that describe the PR flow

Activity

  1. andikrueger
    added a commit that references this issue on Mar 12, 2026

    test: hostile QA scenarios and nasty input corpus (github#350)

    8e3576a
  2. bradygaster
    added
    squadSquad triage inbox — Lead will assign to a member
    squad:mcmanus
    squad:trejo
    priority:p1This sprint
    type:docsDocumentation work
    on Mar 13, 2026
  3. github-actions
    added
    squad:dsky
    go:needs-researchNeeds investigation
    on Mar 13, 2026

  4. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #350 — Docs and changeset base branch guidance are inconsistent
    Assigned to: DSKY (TUI Engineer)
    Reason: Issue relates to frontend/UI work

    @copilot evaluation: No strong capability match — routed to squad member.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  5. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    ⚠️ No squad member found matching label squad:mcmanus. Check .squad/team.md (or .ai-team/team.md) for valid member names.

  6. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    ⚠️ No squad member found matching label squad:trejo. Check .squad/team.md (or .ai-team/team.md) for valid member names.

  7. bradygaster
    added
    status:contributor-invitedA specific contributor has been invited to work on this
    and removed
    squad:dsky
    on Mar 13, 2026
  8. bradygaster
    self-assigned this
    on Mar 13, 2026

  9. bradygaster commented on Mar 13, 2026

    @bradygaster
    bradygaster
    on Mar 13, 2026
    Collaborator

    📌 Brady requested this issue be assigned to @diberry (docs/UX triage). Pending collaborator invite to complete assignment.

  10. bradygaster
    added
    squad:pao
    squad:surgeon
    and removed
    squad:mcmanus
    squad:trejo
    on Mar 13, 2026

  11. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    📋 Assigned to Surgeon (Release Manager)

    Issue: #350 — Docs and changeset base branch guidance are inconsistent

    Surgeon will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    Surgeon, work on issue #350

  12. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    📋 Assigned to PAO (DevRel)

    Issue: #350 — Docs and changeset base branch guidance are inconsistent

    PAO will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    PAO, work on issue #350

  13. diberry
    added a commit that references this issue on Mar 14, 2026

    fix: align baseBranch config and docs to dev

    6c38e7b

  14. bradygaster commented on Mar 15, 2026

    @bradygaster
    bradygaster
    on Mar 15, 2026
    Collaborator

    Thanks for catching this, @matthewcorven. @diberry has PR #393 in progress that addresses the base branch inconsistency between CONTRIBUTING.md and the changeset config. Dina — no rush at all on your docs PRs. Take your time getting them where you want them, and when you're ready, ping @bradygaster and he'll get them merged. Closing this since the fix is underway. 🙌

  15. bradygaster
    closed this as completedon Mar 15, 2026
  16. diberry
    added a commit that references this issue on Mar 15, 2026

    fix: align baseBranch config and docs to dev

    a13c151
  17. bradygaster
    added a commit that references this issue on Mar 15, 2026

    fix: align baseBranch config and docs to dev

    f035429
  18. bradygaster
    removed
    squad:pao
    squad:surgeon
    on Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

go:needs-researchNeeds investigationpriority:p1This sprintsquadSquad triage inbox — Lead will assign to a memberstatus:contributor-invitedA specific contributor has been invited to work on thistype:docsDocumentation work

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions