Repository navigation
Publish the linter badges to a badges branch, not onto the pull request - #87
Merged
Merged
Conversation
The check-abap2UI5 workflow committed the two badge JSONs onto the pull request branch, because main is protected and github-actions[bot] cannot bypass that. That bot commit started a second set of workflow runs which wait for a maintainer's approval (action_required), so every pull request that moved a badge was left blocked. The badges now live on an orphan `badges` branch that holds nothing else: - the publish step runs only on main, after a green gate, and pushes the two files there as a fast-forward; a failed push is a warning - pull request runs publish nothing and check out the default merge ref again - the head branch was only needed to push back - the README reads the badges from the badges branch - .github/badges/ is no longer tracked (every run rewrites it) and is ignored - the weekly bump-linter run no longer restores the badge files - there is nothing tracked to restore The branch is created by the first run on main after this merges; until then the two README badges show "resource not found". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014bLQZPXbB8xmewCNmnBJaG
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.
Why
check-abap2UI5committed the two badge JSONs onto the pull request branch, because main is protected andgithub-actions[bot]cannot bypass that. That bot commit started a second set of workflow runs that wait for a maintainer's approval (action_required), so every pull request that moved a badge was left blocked (#86).Change
badgesbranch that holds nothing else. A failed push is a warning.…/samples-stack/badges/<file>.json..github/badges/: no longer tracked, since every run rewrites it, and added to.gitignore.abap2ui5lint.jsoncand AGENTS.md (.github/paragraph) describe the new path.After merging
check-abap2UI5run on main creates thebadgesbranch. Until it has run, the two README badges show "resource not found".badges.Checks
check:prose,check:samples-md,check:catalogueandcheck:app-rulespass.🤖 Generated with Claude Code
https://claude.ai/code/session_014bLQZPXbB8xmewCNmnBJaG
Generated by Claude Code