Repository navigation
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This branch has not been deployed
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.
Regenerated
openapi.jsonfrom the public REST spec that just shipped to prod.The API reference pages resolve their operations from this spec, so this keeps the published reference in sync with the live API.
Note
Low Risk
Documentation-only OpenAPI sync; no runtime code changes, though clients should adopt new finding and repo response fields if they generate from the spec.
Overview
Regenerates
openapi.jsonso the published API reference matches production (commit a9599d5). Most line churn is JSON formatting (multi-lineenum/tags/requiredarrays); the substantive contract updates are below.Findings now expose required
display_idandnumberon list and detail responses, and document thatGET/PATCH/findings/{id}andPOST/findings/{id}/commentsaccept either a UUID or a display id (e.g.HAC-FD-1104).Repos list entries add required
openFindingsCountandlastScanAtonUnifiedRepoDto.Scans clarify
auth_instructionsas target-site URLs plus browser login/credential instructions.Reviewed by Cursor Bugbot for commit c431d65. Bugbot is set up for automated code reviews on this repo. Configure here.