Repository navigation
[instructions] Document create-issue allowed-fields and fields runtime parameter - #31319
Merged
pelikhan merged 1 commit intoMay 10, 2026
Conversation
…ime `fields` parameter Sync .github/aw/safe-outputs.md with create_issue safe-output behavior shipped in v0.71.x: the YAML config accepts `allowed-fields:` to restrict which issue fields the agent may set, and the runtime tool call accepts a `fields` array for setting custom field values immediately after issue creation. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
pelikhan
deleted the
instructions-sync-v0.71.5-create-issue-fields-08a8d023a37c8609
branch
May 10, 2026 11:58
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.
Instructions Update — Synchronized with v0.71.5
Sync
.github/aw/safe-outputs.mdwithcreate_issuesafe-output behavior already shipped in v0.71.x.Files Changed
.github/aw/safe-outputs.md— added two missing items to thecreate-issue:section:allowed-fields: [Priority, Iteration]to restrict which issue fields the agent may setfields: [{name, value}, ...]array oncreate_issueagent output for setting custom field values on creation, with a JSON exampleWhy
Commit
8f3a4ab('Add fields + allowed-fields support to create_issue safe output') added these capabilities to the compiler (pkg/workflow/create_issue.go:17) and the workflow JSON schema (pkg/parser/schemas/main_workflow_schema.json:4844). The user-facing reference (docs/src/content/docs/reference/safe-outputs.md) already documents both, but the agent-facing instruction file did not — agents writing workflows would not know to expose these to users.Audit Coverage
SafeOutputsConfigstruct inpkg/workflow/compiler_types.goagainst the operations table insafe-outputs.md. All other YAML-keyed operations are present and accurate.comment-memorylives undertools:(extracted viaextractCommentMemoryConfig), not directly undersafe-outputs:, and is correctly documented inmemory.mdandsyntax.md.set-issue-field,dispatch_repository,report-incomplete,actions,scripts,jobsall match their code-level definitions.Size Audit
safe-outputs.mdgithub-agentic-workflows.mdValidation
safe-outputs.md), not the main filecreate-issueblockpkg/workflow/create_issue.go,pkg/parser/schemas/main_workflow_schema.json, and the public reference docs