[instructions] Sync github-agentic-workflows.md with update_project schema changes #8123
Conversation
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
- Clarify usage patterns for different content types - Add explicit example for creating draft issues in Projects v2 - Separate examples for adding existing issues/PRs vs creating drafts - Remove overly prescriptive language in favor of clearer patterns Reflects schema changes from ffd9d2c (removal of oneOf constraint) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
github-actions
bot
added
automation
documentation
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.
Instructions Update - Schema Synchronization
This PR updates the github-agentic-workflows.md file to reflect recent changes to the
update_projectsafe-output schema.Changes Made
update-projectdocumentation to clarify usage patterns for different content typesDocumentation Commits Reviewed
Context
The recent commit removed the
oneOfconstraint from theupdate_projectschema, making it more flexible. The schema now supports:content_type+content_numbercontent_type: "draft_issue"+draft_title+ optionaldraft_bodyThe instructions now better reflect this flexibility and provide clear examples for both use cases.
Validation