Repository navigation
Conversation
|
Flaky tests detected in 9fd0b10. 🔍 Workflow run URL: https://github.com/desrosj/gutenberg/actions/runs/34546322074 should update the HTML only for the latest navigation in
|
desrosj
changed the title
wp/7.1 branch Actions: Remove trunk-only workflowswp/7.1 branch Actions: Remove obsolete and trunk-only workflows
desrosj
force-pushed
the
fix-actions-7.1/remove-rn-workflows
branch
from
September 10, 2026 18:13
82f3382 to
29682c7
Compare
desrosj
marked this pull request as ready for review
September 10, 2026 18:32
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
desrosj
marked this pull request as draft
September 10, 2026 20:11
desrosj
force-pushed
the
fix-actions-7.1/remove-rn-workflows
branch
from
September 10, 2026 23:58
29682c7 to
327e271
Compare
desrosj
marked this pull request as ready for review
September 11, 2026 00:25
desrosj
marked this pull request as draft
September 11, 2026 00:30
desrosj
marked this pull request as ready for review
September 11, 2026 00:39
desrosj
marked this pull request as draft
September 11, 2026 00:40
desrosj
marked this pull request as ready for review
September 11, 2026 00:41
desrosj
force-pushed
the
fix-actions-7.1/remove-rn-workflows
branch
from
September 11, 2026 16:57
9fd0b10 to
d11a0d1
Compare
`storybook-pages.yml` deploys the single canonical Storybook GitHub Pages site and only triggers on pushes to `trunk`; there is one Storybook site for the whole project, not one per branch, so this branch's copy can never run.
`cherry-pick-wp-release.yml` only triggers on pushes to `trunk` or labeled pull requests targeting `trunk`. `wp/X.Y` branches, including this one, are its destination, never its trigger source, so it can never run here. `publish-npm-packages.yml` is kept on this branch per updated project policy.
…oad workflows. `sync-assets-to-plugin-repo.yml` triggers only on `push: branches: [trunk]` events that touch `assets/**`, so it can never run against this branch. `upload-release-to-plugin-repo.yml` is removed too: it triggers on `release: types: [published]`, which isn't literally trunk-restricted, but no release events actually happen in the context of these numbered `wp/X.Y` branches — releases are cut from separate `release/X.Y` branches instead — so it's functionally dead weight here despite the trigger being technically reachable.
`stale-issue-gardening.yml` is schedule-triggered, and GitHub only ever runs a scheduled workflow using the copy on the repository's default branch, regardless of any copy present elsewhere — this branch's copy can never execute. `sync-backport-changelog.yml` triggers on `push: branches: [trunk]` or `issues: types: [labeled]`. The push trigger is trunk-only, and the issue-label trigger isn't tied to any git ref at all — like the schedule case above, GitHub always runs it using the workflow file from the repository's default branch, so this branch's copy is never the one that actually executes for that event either.
`check-backport-changelog.yml` and `check-package-changelogs.yml` both trigger on `pull_request: branches: [trunk]` only, so neither can ever run against a pull request targeting this branch.
desrosj
force-pushed
the
fix-actions-7.1/remove-rn-workflows
branch
from
September 11, 2026 18:15
d11a0d1 to
b7b87c8
Compare
desrosj
removed this pull request from stack #177
September 11, 2026 18:31
desrosj
added this pull request to stack #278
September 11, 2026 18:33
🤖 PR meta 🤖🏁 Flaky testsShow the failuresSome 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. Should save the changes in
|
Owner
Author
|
Migrated to real upstream: WordPress#82787. Closing this fork PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Removes every workflow whose triggers make it trunk-only, from
wp/7.1.check-backport-changelog.ymlpull_request: branches: [trunk]onlycheck-package-changelogs.ymlCHANGELOG.mdupdatespull_request: branches: [trunk]onlystale-issue-gardening.ymlsync-backport-changelog.ymlpush: branches: [trunk], plus anissues: labeledtrigger that — like the schedule case above — isn't tied to any git ref, so GitHub always runs it from the default branch's copy toosync-assets-to-plugin-repo.ymlassets/**to the WordPress.org plugin repopush: branches: [trunk]onlycherry-pick-wp-release.ymlwp/X.Ybranchestrunk; this branch is its destination, never its trigger sourcestorybook-pages.ymlpush: branches: [trunk]onlyupload-release-to-plugin-repo.ymlrelease: types: [published]; in practice, releases are only ever published fromrelease/X.Ybranches, not from numberedwp/X.Ybranches, so this branch is never the context a release actually happens inpull-request-automation.ymltrunkfor its actual logic, regardless of which branch triggered itNo React Native mobile workflows or
gradle-wrapper-validation.ymlexist on this branch at all — it was cut after those were already removed from trunk.Why?
Keeping dead or inapplicable workflow files around adds maintenance surface (stale action pins, lint noise) with no corresponding benefit.
The workflows removed cannot be meaningfully executed against a branch other than
trunk.scheduleevents, the event only ever fires for the default branch.trunk(except minor releases, which come from the respectiverelease/X.Ybranch).Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.