Repository navigation
Improve CI workflows - #87
Merged
Merged
Conversation
Reduce unnecessary CI runs and modernize workflow configuration: - Add branch filters (push only on main) to prevent duplicate runs for PRs - Add path filters so each workflow only triggers for its own component - Add concurrency groups to cancel superseded runs - Pin Node.js 24 via actions/setup-node@v4 - Use local bundle-verifier (./bundle-verifier) instead of published @v1 tag - Remove redundant lint step from compile_test job (covered by lint job) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
pushtriggers only onmainto prevent duplicate CI runs for pull requestscancel-in-progressactions/setup-node@v4withnode-version: 24check-distjob now uses./bundle-verifierinstead ofredhat-actions/common/bundle-verifier@v1, testing against current source rather than a published tagcompile_testjob no longer runsnpm run lintsince the dedicatedlintjob already covers itTest plan
🤖 Generated with Claude Code