Repository navigation
feat: show review progress on the pull request and accept @gitdog - #28
Merged
Merged
Conversation
Each review keeps one status comment on the pull request: reviewing when it starts, then ready for approval, reviewed with a link, no new changes, cancelled, or why it could not finish, with reasons safe for public pull requests. This replaces the separate limit and no-change notices. Commands also run as @GitDog and after another review bot's command on the same line.
|
Visit the preview URL for this PR (updated for commit e9964c6): https://codeyou-df251--pr28-fix-command-aliases-w2bxo47g.web.app (expires Tue, 24 Nov 2026 17:34:14 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 844dad9c62537d028cabc21008e4e2e4031ce4e5 |
…ands Status comments change only on outcomes: an expiry that ended nothing, a running review and a review about to post leave them alone, a late settle re-reads the review before editing, and rejection, a recheck supersede, an approval-setting change and a review that ended before its comment was recorded all update it. A pull request that keeps failing hears about automatic reviews at most once a day, cancellations read as cancelled, and an oversized pull request gets no retry hint. A chained command must follow a known review bot, a chained thank-you posts nothing, and @GitDog belongs to the production app only.
hyochan
commented
Nov 17, 2026
…c reviews Stored failure messages are rewritten for display, so matching them never detected a cancelled review. Generation and publication now record reviewCancelled when the pull request moved on, and a cancelled request still offers a retry. An automatic failure that edits its existing comment starts the daily quiet window too, settle decides before fetching a GitHub token, a settle-posted comment no longer triggers a second settle, and a first review with nothing reviewable says so instead of reporting no new changes. Chained full requires review, the help text offers @GitDog only in production, and Cursor and Codium are known review bots.
hyochan
commented
Nov 17, 2026
Nothing is posted until the review request goes out, so a lifecycle change after the claim is a cancellation, not a GitHub failure. Also drop binary files from the nothing-to-review wording, since a binary-only pull request never reaches it.
hyochan
commented
Nov 17, 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.
Summary
On hyodotdev/openiap#619 Gitdog was reviewing all along (a 255-file batched review), but nothing on the pull request said so, and the
@gitdog reviewcomment was ignored. This PR fixes both.Review progress on the pull request
Commands
@gitdogworks as shorthand for@gitdogbot(the docs note it also notifies the GitHub user of that name).@coderabbitai review @gitdogbot review. The preceding mention must look like a bot (…bot,…ai,copilot,…assist,[bot]), so "@alice I think @gitdogbot review is broken" still does not run one.Production impact
ticketActions.statusCommentId.tickets.pullRequestLimitNoticeAtstays in the schema but is no longer written.issues: write).Test plan
bun run lint && bun run typecheck && bun run build && bun run test && bun run format:check && bun run check:api && bun run typecheck:cli && bun run test:cli@gitdog reviewworks🤖 Generated with Claude Code