Conversation
…files. This adds the workflow-lint.yml workflow (pointed at trunk's reusable reusable-workflow-lint.yml job) to wp/5.9 so it can run against this branch's own .github/workflows/** files and surface whatever actionlint findings, if any, apply here. This is NOT a decision to adopt this workflow permanently on wp/5.9 - it exists purely so the results can be reviewed before deciding whether and how to add it for real.
![github-advanced-security[bot]](https://avatars.github.com/in/57789?s=60&v=4){kind=small}
| security-events: write | ||
| actions: read | ||
| contents: read | ||
| uses: WordPress/gutenberg/.github/workflows/reusable-workflow-lint.yml@trunk |
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
2 participants
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 is this?
This is a disposable evaluation PR, not part of the
fix-actions-5.9/...repair stack forwp/5.9. It exists purely so thepull_request-triggeredworkflow-lint.ymljob actually runs against this branch's real workflow files and surfaces whateveractionlintfindings, if any, apply here.Why is the base
trunkand notwp/5.9?The base of this PR is deliberately set to
trunk, notwp/5.9. This is intentional:wp/5.9would make it look like part of the ongoing repair stack and could get auto-picked-up bygh stacktooling.trunkkeeps it clearly separate and disposable, while still triggering the lint workflow so its results are visible.Because of this, the diff shown here is enormous — it includes all of
wp/5.9's divergence fromtrunk, plus the one new file (.github/workflows/workflow-lint.yml). This is expected. This PR is not meant to be mergeable or reviewed as a real diff.What does the new file do?
It adds
.github/workflows/workflow-lint.ymltowp/5.9, using the project's establishedreference-trunk-workflow-lintlayer template (with branch filters already widened per WordPress#82744) to point at trunk'sreusable-workflow-lint.ymljob.What happens next?
This PR is evaluation only — adding this file here is not a decision to adopt it permanently on
wp/5.9. The user will review the actionlint results from the CI run this PR triggers, then decide separately whether and how to actually adopt this for the branch (e.g. as a real layer in thefix-actions-5.9/...stack).Do not merge this PR.