Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,6 +194,19 @@ When editing PR metadata, preserve the native closing-Issue relationship.
Removing or changing that relationship changes the plan-conformance identity
and intentionally invalidates the affected Code evidence.

### Closing hierarchy validation

When a PR closes a parent with native sub-issues, validate the Close Set in two
stages:

1. Close only the parent while one native child remains open. Confirm
`OpenAI PR Review` fails and names the missing open child.
2. Add the open child to the same native closing-Issue set. Confirm all three
OpenAI Checks pass and the unchanged parent Issue evidence is `reused`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Link the implementation sub-issue for the passing validation case

This claims all three checks pass after adding the child, but the linked context contains only Task #16. #17 owns the implementation work and live validation, so it must be linked and closed for this claimed passing case.

Useful? React with 👍 / 👎.


Already-closed children satisfy the hierarchy and do not need to be repeated
in the current PR. Including an already-closed child is also harmless.

1. Copy `openai-pr-review-dispatch.yml` into the caller repository's default
branch.
2. Replace local reusable-workflow paths with a protected `v1` reference or an
Expand Down
Loading