Add draft_issue content_type support to update_project schema and validation #13113
+216
−65
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.
The
update_projecthandler's JavaScript implementation supports creating draft issues in Projects v2 viacontent_type: "draft_issue", but the schema and Go validation were missing this option.Changes
"draft_issue"tocontent_typeenum and addeddraft_title/draft_bodyproperties"draft_issue"enum value and validation rules fordraft_title(max 256) anddraft_body(max 65000)Usage
{ "type": "update_project", "project": "https://github.com/orgs/myorg/projects/42", "content_type": "draft_issue", "draft_title": "Draft Item Title", "draft_body": "Optional markdown content", "fields": {"Status": "Todo", "Priority": "High"} }The JavaScript implementation in
update_project.cjsalready handles this fully (including 6 test cases). This change completes the type system coverage.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.