[instructions] Sync github-agentic-workflows.md with v0.66.1#24463
Merged
[instructions] Sync github-agentic-workflows.md with v0.66.1#24463
Conversation
Document two changes since v0.66.1 release: - add-comment: document reply_to_id field for discussion thread replies - steps/post-steps: document secrets expression restriction (strict mode error) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.66.1
This PR updates
github-agentic-workflows.mdbased on changes since the v0.66.1 release.Changes Made
add-comment—reply_to_idfor discussion threading: Document the newreply_to_idagent output field that enables threaded replies within GitHub Discussions (shipped in v0.66.1).steps/post-steps— secrets restriction: Document the compiler check (added post-release in Add compiler check disallowing secrets expressions in custom steps #24450) that treats$\{\{ secrets.* }}expressions (excludingsecrets.GITHUB_TOKEN) in custom steps as an error in strict mode and a warning otherwise.Documentation Commits Reviewed
e255fc7Add compiler check disallowing secrets expressions in custom steps (Add compiler check disallowing secrets expressions in custom steps #24450)Safe-Outputs Code Audit
Audited
SafeOutputsConfigincompiler_types.goandsafe_outputs_config.goagainst the instructions file. All operations currently defined in code (create-issue,add-comment,create-pull-request,create-pull-request-review-comment,submit-pull-request-review,reply-to-pull-request-review-comment,resolve-pull-request-review-thread,create-discussion,update-discussion,close-discussion,close-issue,close-pull-request,mark-pull-request-as-ready-for-review,update-issue,update-pull-request,push-to-pull-request-branch,upload-asset,update-release,add-labels,remove-labels,add-reviewer,assign-milestone,link-sub-issue,hide-comment,set-issue-type,dispatch-workflow,dispatch_repository,call-workflow,create-code-scanning-alerts,autofix-code-scanning-alert,create-agent-session,update-project,create-project,create-project-status-update,assign-to-agent,assign-to-user,unassign-from-user,missing-tool,missing-data,noop,threat-detection,jobs,scripts,actions) are documented in the instructions file. Theauthfield on HTTP MCP servers is also already documented.Validation