Repository navigation
UID2-7426: add check_jira_key required-status-check caller - #49
Merged
Merged
Conversation
BehnamMozafari
approved these changes
Jul 7, 2026
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
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.
What
Adds
.github/workflows/check-jira-key.yaml— the caller for thecheck_jira_keyrequired-status-check (UID2-7426). First of ~24 identical rollouts, opened alone for review before fanning out to the rest.Behaviour
pull_request(opened / edited / synchronize / reopened) and callsIABTechLab/uid2-shared-actions/actions/check_jira_key@v3.UID2-<n>key or a reasoned[no-jira - reason: <reason>]opt-out (mirrors the native ruleset on the enterprise orgs; IABTechLab is team-plan so the native rule is inert there).required_status_checksrule is flipped on (separate step, after a bake).check_jira_keyso every repo yields the same status-check context → one terraform required-check entry matches all 24.Merge only after
uid2-shared-actions#254 is merged and a release has moved thev3tag to includeactions/check_jira_key. Otherwise, once this lands onmain, future PRs here would fail to resolve the action at@v3.(Safe to leave open in the meantime:
pull_requestworkflows run from the base branch, which doesn't have this file yet, so the check does not run on this PR itself.)Rollout
Once this shape is approved, the identical file goes to the other 23 in-scope IABTechLab
uid2*repos.