YETUS-1278. Restore commit statuses under GHA with stable context keys#388
Open
ndimiduk wants to merge 1 commit into
Open
YETUS-1278. Restore commit statuses under GHA with stable context keys#388ndimiduk wants to merge 1 commit into
ndimiduk wants to merge 1 commit into
Conversation
YETUS-1277 removed all per-sub-check commit statuses under GitHub Actions to avoid stale statuses on re-run (severity was encoded in the context key, so re-runs created new entries instead of overwriting). This left push-event consumers with no per-check visibility in the GitHub UI. Replace the blanket skip with two targeted fixes: - Use GITHUB_JOB in the header so concurrent workflows don't collide - Drop severity prefix from context keys so re-runs overwrite correctly
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.
YETUS-1277 removed all per-sub-check commit statuses under GitHub Actions to avoid stale statuses on re-run (severity was encoded in the context key, so re-runs created new entries instead of overwriting). This left push-event consumers with no per-check visibility in the GitHub UI.
Replace the blanket skip with two targeted fixes: