Skip to content

Commit 32571ef

Browse files
cliffhallclaude
andcommitted
docs(contribution-model): drop the transitional blank-issue wording
The issue forms reach main with #4939 and config.yml disables blank issues, so "until then the chooser offers a blank issue" goes stale. State the steady-state rule instead, as CONTRIBUTING.md now does. Closes #4962 Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: cliffhall <[email protected]>
1 parent b92af77 commit 32571ef

1 file changed

Lines changed: 3 additions & 4 deletions

File tree

‎docs/contribution-model.md‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,9 @@ Where the policy is stated:
3333
| `src/fetch/README.md`, `src/time/README.md` | Their Contributing sections, which are published to PyPI |
3434

3535
⚠️ **GitHub serves the issue forms and `config.yml` from the default branch**
36-
(`main`). Development happens on `v2/main`, so the forms go live at the first
37-
milestone merge that contains them. Until then the chooser offers a blank issue,
38-
and the close comments below point at the policy on `v2/main`, where it already
39-
applies.
36+
(`main`). Development happens on `v2/main`, so a change to them goes live at
37+
the next milestone merge, not when it merges into `v2/main`. The close comments
38+
below point at the policy on `v2/main`, where a change to it lands first.
4039

4140
## The backlog at the time of writing
4241

0 commit comments

Comments
 (0)