Repository navigation
ci: standardize workflow and action display names - #21
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.
Use consistent workflow titles and explicit job/action-step display names. Job and step IDs, commands, permissions, triggers, workflow paths, artifact identities and inputs/outputs are unchanged.
Validation: actionlint 1.7.12, parsed before/after comparison of executable YAML, and deterministic naming-policy audit passed locally. Hosted CI must pass at the exact head before merge.
Required-check names: ci → Test. Migrate these exact settings only after replacement checks pass; preserve strict mode, GitHub App bindings and the number of required checks.
Workflow security guard selectors now use stable step IDs, action identities or release operations instead of display labels. The trusted checkout, SHA pinning, publication ordering and negative security assertions remain enforced. Focused guard checks pass locally; full hosted CI remains required.