This was generated by AI during triage.
Why
specgit issue derives a draft pull request against the repository default branch (main). This repository requires feature/fix/chore deliveries to enter through dev; during #519 the generated PR #520 therefore targeted the wrong integration tier until manually retargeted.
The wrong base starts main-only acceptance work, bypasses the intended fast integration layer, and creates a merge-risk if it is not noticed immediately.
Scope
Out of scope: changing GitHub's default branch or weakening either branch ruleset.
Acceptance
- A new SpecGit delivery opened from an allowed delivery branch has
baseRefName == "dev" without a manual gh pr edit step.
- The bootstrap fails clearly if it cannot verify or correct the PR base.
- Tests cover the configured
dev target and preserve SpecGit's default behavior outside this repository-specific path.
Dependency
Why
specgit issuederives a draft pull request against the repository default branch (main). This repository requires feature/fix/chore deliveries to enter throughdev; during #519 the generated PR #520 therefore targeted the wrong integration tier until manually retargeted.The wrong base starts main-only acceptance work, bypasses the intended fast integration layer, and creates a merge-risk if it is not noticed immediately.
Scope
devas the delivery PR base.Out of scope: changing GitHub's default branch or weakening either branch ruleset.
Acceptance
baseRefName == "dev"without a manualgh pr editstep.devtarget and preserve SpecGit's default behavior outside this repository-specific path.Dependency