Conversation
e3be481 to
edaf670
Compare
edaf670 to
8da264f
Compare
a492c00 to
bfc136c
Compare
| @@ -33,4 +41,4 @@ | |||
| security-events: write | |||
| actions: read | |||
| contents: read | |||
| uses: ./.github/workflows/reusable-workflow-lint.yml | |||
| uses: WordPress/gutenberg/.github/workflows/reusable-workflow-lint.yml@trunk | |||
|
Flaky tests detected in 65b0018. 🔍 Workflow run URL: https://github.com/desrosj/gutenberg/actions/runs/34549551369 Save flow should work as expected in
|
bfc136c to
195583c
Compare
195583c to
65b0018
Compare
|
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. |
Removes the local `reusable-workflow-lint.yml` and points `workflow-lint.yml` at `WordPress/gutenberg/.github/workflows/reusable-workflow-lint.yml@trunk` instead, so this branch always lints against trunk's current lint logic rather than a stale local copy. Also widens `workflow-lint.yml`'s own `push`/`pull_request` branch filters from `trunk` only to also include `release/[0-9]+.[0-9]`, `wp/[0-9]+.[0-9]`, `wp/latest`, and `wp/next` — porting `WordPress#82744`'s fix for this file. Without this, pushes or pull requests targeting this branch itself never triggered linting at all, since `trunk` was the only branch the filter recognized.
65b0018 to
1292fd5
Compare
|
Migrated to real upstream: WordPress#82799. Closing this fork PR. |
What?
.github/workflows/reusable-workflow-lint.ymland pointsworkflow-lint.ymlatWordPress/gutenberg/.github/workflows/reusable-workflow-lint.yml@trunkinstead.wp/X.Ybranches.Why?
Linting workflow files helps prevent incorrect and/or insecure patterns from being introduced into the codebase.
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.