-
Notifications
You must be signed in to change notification settings - Fork 312
fix(ci): ignore resolved Codex inline findings #1002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Komzpa
wants to merge
1
commit into
Soju06:main
from
Komzpa:fix/codex-label-ignore-resolved-review-comments
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
19 changes: 19 additions & 0 deletions
19
openspec/changes/ignore-resolved-codex-inline-findings/proposal.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| ## Why | ||
|
|
||
| The Codex review label synchronizer can keep `π€ codex: needs work` on a PR | ||
| after a maintainer resolves an inline Codex finding. The unresolved-thread check | ||
| already knows resolved review threads are no longer blockers, but the timeline | ||
| classifier still merges the old inline review comment and treats it as current | ||
| needs-work evidence. | ||
|
|
||
| ## What Changes | ||
|
|
||
| - Ignore inline Codex finding comments from resolved or outdated review threads | ||
| when computing current-head review state. | ||
| - Keep unresolved inline Codex finding comments as needs-work evidence. | ||
| - Add regression coverage for both resolved and unresolved inline findings. | ||
|
|
||
| ## Impact | ||
|
|
||
| - GitHub automation only. | ||
| - No application runtime behavior changes. |
23 changes: 23 additions & 0 deletions
23
...c/changes/ignore-resolved-codex-inline-findings/specs/github-automation/spec.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| ## MODIFIED Requirements | ||
|
|
||
| ### Requirement: Codex review label sync review-thread state | ||
|
|
||
| The Codex label synchronization script MUST treat unresolved, non-outdated | ||
| Codex inline review findings on the current head as needs-work evidence. It | ||
| MUST NOT treat inline Codex findings from resolved or outdated review threads as | ||
| active needs-work evidence. | ||
|
|
||
| #### Scenario: Resolved inline finding no longer blocks the ok label | ||
|
|
||
| - **WHEN** a current-head inline Codex finding comment belongs to a resolved | ||
| review thread | ||
| - **AND** a clean current-head Codex review exists | ||
| - **THEN** the script does not classify that inline finding as active | ||
| needs-work evidence | ||
|
|
||
| #### Scenario: Unresolved inline finding still blocks the ok label | ||
|
|
||
| - **WHEN** a current-head inline Codex finding comment belongs to an unresolved, | ||
| non-outdated review thread | ||
| - **THEN** the script classifies that inline finding as active needs-work | ||
| evidence | ||
6 changes: 6 additions & 0 deletions
6
openspec/changes/ignore-resolved-codex-inline-findings/tasks.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| ## Implementation | ||
|
|
||
| - [x] Filter current-head inline Codex finding comments by unresolved review-thread URLs. | ||
| - [x] Preserve unresolved inline finding comments as needs-work evidence. | ||
| - [x] Add unit coverage for resolved and unresolved inline findings. | ||
| - [x] Validate the focused test and OpenSpec gates. |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This delta is under
MODIFIED Requirements, butopenspec/specs/github-automation/spec.mddoes not contain an existing requirement namedCodex review label sync review-thread state; it currently only defines the write-token fallback and write-denial resilience requirements. OpenSpec treatsMODIFIEDas changes to an existing requirement, so strict validation/archive will fail for this change instead of accepting the new review-thread-state contract. Since this is a new requirement, move it underADDED Requirementsor add the matching base requirement first.Useful? React with πΒ / π.