Repository navigation
fix(commitments): classify self assignments as own work - #96
Merged
Merged
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 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.
Self-assigned commitments now appear as the user's work instead of waiting for another person. Memory returns
owner: nullfor an owned Person with the boolean self marker, across create, owner-change, open, candidate, list, and detail responses. Same-name contacts remain external owners.Self assignment remains supported: its claim ID, stored
ASSIGNED_TOrelation, history, and assignment filters are preserved. Existing affected records are corrected when read; no data migration or repair is required. The server must be deployed to activate this behavior. Petals PR #405 updates mutation confirmations to use the response.Validation: 50 focused tests passed with real PostgreSQL, including create/reassign and multiple active partitions. The expanded workspace suite also passed after adding deleted-source and strict boolean-marker checks. Type/structured-output checks, lint, format, server build, and SDK build passed. A fresh read-only review found no material issues. Coverage percentage was not measured.
Fixes #91.