Shorten the author reminder comment - #276
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Shortens and clarifies the author reminder.
Changes:
- Replaces the long reminder with two actionable bullets.
- Updates tests and documentation for the revised wording.
- Removes snapshot and command-binding explanations.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
pull-request-dashboard/README.md |
Documents the shorter reminder. |
.github/scripts/pull-request-dashboard/test_author_nudge.py |
Updates reminder assertions. |
.github/scripts/pull-request-dashboard/author_nudge.py |
Generates the revised reminder. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
trask
marked this pull request as ready for review
August 20, 2026 15:25
trask
marked this pull request as draft
August 20, 2026 15:25
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
trask
marked this pull request as ready for review
August 20, 2026 15:33
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
Suppressed comments (2)
pull-request-dashboard/README.md:244
- “Replying” is broader than the documented behavior: a reply that commits to future work remains with the author (lines 124-130 and 151-165). Qualify this as a completed reply so this summary does not contradict the lifecycle rules above.
replying is enough to resume normal approval-based routing, and advertises
.github/scripts/pull-request-dashboard/author_nudge.py:329
- This reminder is also posted while the author route is held by required checks or Copilot review (
test_author_nudge.py:381-391), but those gates keep the route atauthoreven after a review reply (dashboard.py:1567-1626), and failing checks force the author route independently (dashboard.py:1253-1255). In those cases replying does not hand off the pull request, so the reminder can remain active after the author follows this instruction. Please scope this bullet to clearing review items and say that onward routing waits for any other author-owned blockers; update the matching test assertion as well.
"- Replying is enough to hand it off — answer, explain why no change is "
"needed, or ask a follow-up. The dashboard routes it onward "
"automatically.",
Pull request dashboard statusMerged · refreshed 2026-08-20 23:58 UTC Status above doesn't look right?
|
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
maryliag
approved these changes
Aug 20, 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.
The author reminder comment was five paragraphs, and most of it explained the mechanism rather than telling the author what to do. It now leads with the link to the live status and gives two bullets: reply, or hand it back.
The first bullet does not name where the pull request goes next, and does not promise that a reply alone moves it. Routing depends on approvals, so an already-approved pull request can go straight to maintainers, and a failing required check keeps the pull request with the author no matter what the author says.
The second bullet no longer justifies the command by the author needing reviewer help, because that framing left no room for the case where routing is simply wrong. Naming that case invites authors to use the command instead of arguing with the bot in prose.
Dropped: the snapshot footer, since the sentence above it already says the linked comment is kept current, and the explanation of how the command binds to the head it sees, which authors do not need in a reminder.
Already-posted reminders keep the old wording. Nothing rewrites an existing nudge body, and adding that is not worth the complexity for a one-time wording change.