Repository navigation
Conversation
…files. This points at trunk's reusable lint job (reusable-workflow-lint.yml@trunk) purely to see what actionlint findings, if any, apply to wp/6.7's own workflow files. This is NOT yet a decision to adopt the file permanently on this branch — it exists purely so the user can review real findings before deciding.
| security-events: write | ||
| actions: read | ||
| contents: read | ||
| uses: WordPress/gutenberg/.github/workflows/reusable-workflow-lint.yml@trunk |
This branch has not been deployed
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 is this?
This is a disposable evaluation PR, not part of the
fix-actions-6.7/...repair stack forwp/6.7. It is a completely standalone, one-off addition used purely to see whatactionlintfindings (if any) apply towp/6.7's own current workflow files.wp/6.7currently has no.github/workflows/workflow-lint.ymlfile at all. This PR adds one — copied from the project's establishedreference-trunk-workflow-lintlayer template (branch filters already widened per WordPress#82744) — so thepull_request-triggered lint job actually runs againstwp/6.7's real workflow files and produces visible findings.Why the base is
trunk, notwp/6.7The base of this PR is deliberately set to
trunk, notwp/6.7. This is intentional:wp/6.7would make it look like part of the repair stack and riskgh stacktooling auto-picking it up.trunkkeeps it clearly separate and disposable, and still triggers thepull_requestevent so the newworkflow-lint.ymljob runs.As a result, the diff shown here will look enormous — it includes all of
wp/6.7's accumulated divergence fromtrunkplus the one new file. That's expected and not a mistake. This PR is not meant to be mergeable or reviewed as a real diff; it exists solely to trigger CI and surface real findings.What happens next
The user will separately decide whether/how to actually adopt
workflow-lint.ymlforwp/6.7for real (e.g., as a proper layer added to the repair stack). This PR itself should not be merged — it can be closed once the CI run's findings have been reviewed.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.