Repository navigation
feat!: Leave pull requests to the calling workflow - #3
Merged
Merged
Conversation
This reverts commit a1e8c88. Reason: the override label is a pull request concern, so it belongs in the calling workflow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The CLI no longer posts PR comments, reads the GitHub event, writes the job summary, or checks for pull_request_target. It lints a changeset or files, prints a report in the chosen format, and exits 0, 1, or 2 like eslint and ruff. A new markdown format prints the report for a workflow to post, and prints nothing when there is nothing to report. Setup errors go to stderr, and a crash exits 2 so a caller never reads it as findings. BREAKING CHANGE: --pr-comment is removed; post the markdown report from the workflow, as the README shows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 362894c. Configure here.
| cat report.md >> "$GITHUB_STEP_SUMMARY" | ||
|
|
||
| if [ "$status" -ne 0 ] && [ "$OVERRIDDEN" = true ]; then exit 0; fi | ||
| exit "$status" |
There was a problem hiding this comment.
Override label masks setup failures
High Severity
The workflow exits 0 for every non-zero status when OVERRIDDEN is true, so a setup error or crash (exit 2) also passes the check. Only exit 1 means findings, which the earlier comment and the previous CLI both required.
Reviewed by Cursor Bugbot for commit 362894c. Configure 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.
The CLI no longer knows pull requests exist. It lints a changeset or files, prints a report in the chosen format, and exits 0, 1, or 2 like eslint and ruff, so the calling workflow owns the PR comment and any override label. A new
markdownformat prints the report for the workflow to post and prints nothing when there is nothing to report; setup errors go to stderr, and a crash exits 2 so a workflow never reads it as findings.This reverts #2, which taught the CLI about an override label. Labels and comments are a CI concern, and keeping them out leaves the CLI usable anywhere a changeset or file list is.
--pr-commentis removed, so this is a breaking change for 0.1.0 users; the README's workflow shows how to post the report, add the override guidance, and pass the check with the label.🤖 Generated with Claude Code