Skip to content

Add iteration issue template#77113

Merged
ramonjd merged 5 commits intotrunkfrom
add/iteration-issue-template
Apr 8, 2026
Merged

Add iteration issue template#77113
ramonjd merged 5 commits intotrunkfrom
add/iteration-issue-template

Conversation

@annezazu
Copy link
Copy Markdown
Contributor

@annezazu annezazu commented Apr 7, 2026

Summary

Test plan

🤖 Generated with Claude Code

Adds a GitHub issue template for tracking iteration/release cycle work.
This standardizes the format used across existing iteration issues to
include an overall goal, release scope, task checklist, and stretch goals.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@annezazu annezazu requested a review from desrosj as a code owner April 7, 2026 20:54
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 7, 2026

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: annezazu <annezazu@git.wordpress.org>
Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: andrewserong <andrewserong@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

annezazu and others added 2 commits April 7, 2026 13:58
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@annezazu annezazu added [Type] Task Issues or PRs that have been broken down into an individual action to take [Type] Project Management Meta-issues related to project management of Gutenberg labels Apr 7, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 7, 2026

Flaky tests detected in ffec141.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/24113956664
📝 Reported issues:

@andrewserong andrewserong removed the [Type] Task Issues or PRs that have been broken down into an individual action to take label Apr 7, 2026
@andrewserong
Copy link
Copy Markdown
Contributor

Just removing one label from this issue to please the Github Action that checks that only one "Type" label is attached 🙂

Copy link
Copy Markdown
Contributor

@andrewserong andrewserong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this, I don't think we can test before merge, but this LGTM!

(As an aside, love the idea: the comments read well and this looks like a useful guide for contributors to structure planning for iteration issues 👍)

---
name: Iteration issue
about: Track the scope and tasks for a feature or focus area during a release cycle
labels: "[Type] Iteration"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we could add a title: to prefill the title field, e.g., title: "[Feature Name] iteration for WordPress X.X"

Not a blocker and can be added later.

Copy link
Copy Markdown
Member

@ramonjd ramonjd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I'll merge it in and test (just created a new iteration issue, so I can add these new headings 🍺 )

Thank you!

@ramonjd ramonjd enabled auto-merge (squash) April 8, 2026 02:11
@ramonjd ramonjd merged commit 397e16d into trunk Apr 8, 2026
40 checks passed
@ramonjd ramonjd deleted the add/iteration-issue-template branch April 8, 2026 02:52
@github-actions github-actions bot added this to the Gutenberg 23.0 milestone Apr 8, 2026
@andrewserong
Copy link
Copy Markdown
Contributor

All looking good after merge:

image image

🎉

@annezazu
Copy link
Copy Markdown
Contributor Author

annezazu commented Apr 8, 2026

Gosh, thank you all for seeing this through and making it better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Project Management Meta-issues related to project management of Gutenberg

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants