chore(linear-setup): rename greptile* flags to dojoCodeReviewer* (Greptile uninstall)#24
Merged
Merged
Conversation
…ptile uninstall — DOJ-4574 sibling) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
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
Renames Greptile flags in
linear-setup.jsonto the new dojo-code-reviewer naming.greptileReview->dojoCodeReviewergreptileMinConfidence->dojoCodeReviewerMinConfidenceWhy
Part of the Greptile uninstall (audit 2026-05-28). The reviewer-bot side (dojo-code-reviewer) is already operational per DOJ-4475 + DOJ-4476; this PR aligns the per-repo Linear setup config with the new naming.
Scope
This is a 1-file config rename. No code change. No CI/workflow change.
HITL
Draft per HITL boundary — user decides ready-to-merge.
Created by Claude Code on behalf of @lapc506