Fix Stale Version Comment on the merge-bot-task.yml Pin - #92
Conversation
The earlier bulk pin bump (a72c48c) replaced every hub-workflow SHA in this repo but kept each file's existing trailing comment unchanged. merge-bot-pull-request.yml's comment convention is a version tag rather than the 'main promotion' label the other five uses carry, and review on the main-promotion PR caught that the new SHA (b823bc4...) is tagged 2.0.512 upstream, not the 2.0.380 the stale comment still named. Confirmed via git tag --points-at against the hub.
PR Summary by QodoCorrect merge-bot workflow version annotation
AI Description
High-Level Assessment
Files changed (1) |
Code Review by Qodo🐞 Bugs (0)📘 Rule violations (0)📎 Requirement gaps (0)Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full |
There was a problem hiding this comment.
🟢 Approval recommended
The change corrects a comment-only mismatch without altering workflow behavior, and the remaining note is a non-blocking maintainability suggestion.
Pull request overview
Updates the trailing version comment on the pinned hub reusable workflow reference so it matches the already-updated SHA and doesn’t misreport the upstream tag.
Changes:
- Fixes the stale
# 2.0.380comment to# 2.0.512for themerge-bot-task.ymlpin.
File summaries
| File | Description |
|---|---|
| .github/workflows/merge-bot-pull-request.yml | Updates the pinned workflow’s trailing version comment to reflect the correct upstream tag for the existing SHA. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Review on the main-promotion PR (#91) caught that the earlier bulk pin bump (a72c48c) kept
merge-bot-pull-request.yml's trailing version comment unchanged while bumping its SHA.b823bc4...is tagged2.0.512upstream (confirmed viagit tag --points-atagainst the hub),not the
2.0.380the stale comment still named. The other five hub-workflowuses:in this repouse a
# main promotionlabel instead, which never goes stale this way; this is the only one ona version-tag convention.
🤖 Generated with Claude Code