Fix incoherent close reason wording#29
Open
xthunder0 wants to merge 1 commit intoopenclaw:mainfrom
Open
Conversation
Render incoherent close reasons with wording that no longer collides with not_actionable_in_repo, and tighten the review prompt so incoherent covers unclear or internally contradictory reports rather than generally unactionable ones. Co-Authored-By: Teddy CML <xthunder0@users.noreply.github.com>
xthunder0
force-pushed
the
codex/close-reason-vocabulary
branch
from
e5b7d11 to
1cf8723
Compare
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
2 participants
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
incoherentclose reasons astoo unclear to act onso report prose no longer collides withnot_actionable_in_repo.incoherentcovers unclear or internally contradictory reports, not generally unactionable ones.Fixes #28.
Verification
pnpm run checkpassed.Notes
v22.22.1whilepackage.jsonrequests>=24.