Normalize CI naming - #2
Merged
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.
Background
The baseline workflow still uses repository-specific file, workflow, and job names. Stack repository conventions use
.github/workflows/ci.yaml, workflow nameCI, and the actual required-check contextbaseline.Implementation
.github/workflows/repository.ymlto.github/workflows/ci.yaml.CI.baselineand remove its redundant display name.bootstrappush trigger now thatmainis the default branch.Testing
origin/main.git diff --check origin/main...HEAD.Review focus / concerns
Confirm that GitHub Actions reports the required-check context as
baseline. This changes CI naming and branch targeting only; it does not change theme behavior or licensing policy.