fix: prevent greetings workflow 0-job failure runs on push/synchronize events#550
Draft
Copilot wants to merge 2 commits intobolt-priority-engine-opt-v2-17124686792412411432from
Draft
Conversation
🙏 Thank you for your contribution, @Copilot!PR Details:
Quality Checklist:
Review Process:
Note: The maintainers will monitor code quality and ensure the overall project flow isn't broken. |
Co-authored-by: RohanExploit <178623867+RohanExploit@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix workflow check failures and ensure all run
fix: prevent greetings workflow 0-job failure runs on push/synchronize events
Mar 15, 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.
Description
greetings.ymlwas producingfailureworkflow runs with 0 jobs whenever a branch was pushed. GitHub evaluatespull_request_targetworkflows on push/synchronize events; since the workflow only declaredtypes: [opened], no jobs were scheduled — and GitHub marks 0-job runs asfailure.Fix: Add an explicit
if:guard to thegreetingjob:When the job condition is false, GitHub skips it (run concludes
success) instead of creating an empty run that fails. No change to functional behavior onissues: openedorpull_request_target: openedevents.The other three workflows (
pr-issue-bot.yml,assign-pr-author-on-merge.yml,auto-close-mentioned-issues.yml) already have job-levelif:guards and were not affected.Type of Change
Related Issue
Testing Done
Screenshots (if applicable)
Checklist
Co-Authors
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Summary by cubic
Prevents phantom CI failures by adding an event guard to the greetings workflow so it only runs on
issuesandpull_request_target. Other workflows already had proper guards, so this eliminates 0‑job failures on push/synchronize and restores green checks.Written for commit 96c60cd. Summary will update on new commits.