docs(site): document assignee fallback to last git author in create-work-item#847
Merged
jamesadevine merged 1 commit intoJun 5, 2026
Conversation
…ork-item When 'assignee' is omitted from the create-work-item configuration, the executor falls back to the email of the last person who committed changes to the agent source markdown file, discovered via 'git log' at Stage 3. This behaviour was in docs/safe-outputs.md but missing from the site reference page. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jamesadevine
deleted the
docs/create-work-item-assignee-fallback-4c4c752fe9e0fc8f
branch
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
1 participant
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.
Summary
create-work-itemsafe-output reference more accurate: whenassigneeis omitted from the front-matter config, Stage 3 automatically falls back to the email of the last person who committed changes to the agent's source markdown file (viagit log -1 --format='%ae'). This behaviour was indocs/safe-outputs.mdbut missing from the site page.Changes
site/src/content/docs/reference/safe-outputs.mdx: expandassigneeconfig field description with the git-log fallback behaviour.Accuracy checks
src/safeoutputs/create_work_item.rsline 361:config.assignee.as_ref().or(ctx.agent_last_author.as_ref()).ctx.agent_last_authoris populated bydiscover_last_author()insrc/main.rswhich runsgit log -1 --format='%ae'against the source markdown path at Stage 3 startup.docs/safe-outputs.md(source-of-truth) to site mdx to confirm this was the only meaningful content gap.Validation
cd site && npm ci && npm run buildCreated by the docs-writer workflow.