fix(ci): repair unparseable permissions scalar (2 workflow file(s)) - #218
Merged
Merged
Conversation
A scalar `permissions: read-all` followed by an indented ` actions: read` is a YAML parse error, so the workflow never starts. It emits no check run at all, which means a required context silently never reports and the repository looks greener than a repaired one. `read-all` already grants `actions: read`, so deleting the stray line is a semantic no-op. Verified with a real parser: each file fails `yq` before the change and parses after it. Files: clusterfuzzlite.yml e2e.yml Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0178nN4Nm3neFRy5K9StZKnB
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (30)
📝 SummarySummary by CodeRabbit
WalkthroughThe workflows now use read-only default ChangesWorkflow permission settings
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The workflows retain read-only token permissions, with no identified merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the workflow gate Comment |
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
hyperpolymath
enabled auto-merge (squash)
September 14, 2026 22:16
hyperpolymath
disabled auto-merge
September 15, 2026 15:02
hyperpolymath
deleted the
fix/workflow-permissions-scalar-parse-error
branch
September 15, 2026 15:02
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
1 participant
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.
permissions: read-allfollowed by an indentedactions: readis a YAMLparse error. The workflow never starts, so it emits no check run — a
required context silently never reports, and this repository currently looks
greener than a repaired one.
read-allalready grantsactions: read, so removing the stray line is asemantic no-op. Each file was verified with a real YAML parser: it fails
yqbefore the change and parses after it. Every diff is exactly one deleted line.Files changed: clusterfuzzlite.yml e2e.yml
Measured estate-wide: 42 such files across 28 repositories on
main, allcarrying the identical stray key. Zero overlap with the TokenPermissions sweep.
🤖 Generated with Claude Code
https://claude.ai/code/session_0178nN4Nm3neFRy5K9StZKnB