ci: avoid duplicate PR runs and update badge actions - #159
Merged
Conversation
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.
Summary
Why
Maintainer branches currently trigger the same nine CI and nine GORM jobs twice: once for push and once for pull_request. Restricting push runs to master halves PR compute without reducing coverage.
The latest badge-action releases both use Node 24. The current badge run still warns about Node 20 in dynamic-badges-action v1.7.0, while v1.9.0 also includes the maintainers current 2026 GitHub API update and more reliable async request handling.
Validation
The GIST_SECRET still needs owner rotation; this removes the runtime warning and keeps the workflows current, but does not pretend a code change can replace that credential.