"/repos/OWNER/REPO/pulls/PR_NUMBER" update PR to draft not working

[isaquebc]

Select Topic Area

Bug

Body

I'm doing a bot to convert automatically a PR to draft with a timeout. Here on the company that I'm working, we have a workflow, when a PR is ready to review, we just create a environment and deploy the current version to it. Now we have to convert the PR to draft to kill this environment and I can't do it through the REST API.

I'm doing this curl above:

curl -v -L \
  -X PATCH \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer ${GITHUBTOKEN}" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  "https://api.github.com/repos/${OWNER}/${REPO}/pulls/${PR_NUMBER}" \
  -d '{"draft":true}'

And getting 200 on the request.
This is the log from -v param:

*   Trying 20.201.28.148:443...
* TCP_NODELAY set
* Connected to api.github.com (20.201.28.148) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.github.com
*  start date: Feb  5 00:00:00 2025 GMT
*  expire date: Feb  5 23:59:59 2026 GMT
*  subjectAltName: host "api.github.com" matched cert's "*.github.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo ECC Domain Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55987132adc0)
> PATCH /${OWNER}/${REPO}/pulls/${PR_NUMBER} HTTP/2
> Host: api.github.com
> user-agent: curl/7.68.0
> accept: application/vnd.github+json
> authorization: Bearer ${GITHUBTOKEN}
> x-github-api-version: 2022-11-28
> content-length: 51
> content-type: application/x-www-form-urlencoded
> 
* We are completely uploaded and fine
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 200 
< date: Mon, 14 Apr 2025 13:04:55 GMT
< content-type: application/json; charset=utf-8
< content-length: 21633
< cache-control: private, max-age=60, s-maxage=60
< vary: Accept, Authorization, Cookie, X-GitHub-OTP,Accept-Encoding, Accept, X-Requested-With
< etag: "******"
< github-authentication-token-expiration: ****-**-** 17:49:16 -0
< x-github-media-type: github.v3; format=json
< x-accepted-github-permissions: pull_requests=write
< x-github-api-version-selected: 2022-11-28
< x-ratelimit-limit: 5000
< x-ratelimit-remaining: 4997
< x-ratelimit-reset: 1744638640
< x-ratelimit-used: 3
< x-ratelimit-resource: core
< access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset
< access-control-allow-origin: *
< strict-transport-security: max-age=31536000; includeSubdomains; preload
< x-frame-options: deny
< x-content-type-options: nosniff
< x-xss-protection: 0
< referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin
< content-security-policy: default-src 'none'
< server: github.com
< x-github-request-id: DE1A:****:****:****:****
< 

The response is:

{
  "url": "https://api.github.com/repos/${OWNER}/${REPO}/pulls/${PR_NUMBER}",
  "id": ****,
  "node_id": "******",
  "html_url": "https://github.com/${OWNER}/${REPO}/pull/${PR_NUMBER}",
  "diff_url": "https://github.com/${OWNER}/${REPO}/pull/${PR_NUMBER}.diff",
  "patch_url": "https://github.com/${OWNER}/${REPO}/pull/${PR_NUMBER}.patch",
  "issue_url": "https://api.github.com/repos/${OWNER}/${REPO}/issues/${PR_NUMBER}",
  "number": ${PR_NUMBER},
  "state": "open",
  "locked": false,
  "title": "Implementing timeout on exp envs",
  ...
  "milestone": null,
  "draft": false,
  "commits_url": "https://api.github.com/repos/${OWNER}/${REPO}/pull/${PR_NUMBER}/commits",
  ...
}

I expected that this request would convert this PR to draft. But it was not converted.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[isaquebc]

I tried using github cli, it's not working too

I have tried In this way:

gh api   -H "Accept: application/vnd.github.shadow-cat-preview+json"   -X PATCH "repos/${OWNER}/${REPO}/pulls/${PR_NUMBER}"   -f draft=true

The response is success, but when I check using this command:

gh pr view feature/exp-env-timeout --json isDraft

The result still beeing

{
  "isDraft": false
}

The other way was using the edit from gh:

gh pr edit ${BRANCH_NAME} --draft

But it said that --draft isn't a valid flag:

unknown flag: --draft

Usage:  gh pr edit [<number> | <url> | <branch>] [flags]

Flags:
      --add-assignee login      Add assigned users by their login. Use "@me" to assign yourself.
      --add-label name          Add labels by name
      --add-project title       Add the pull request to projects by title
      --add-reviewer login      Add reviewers by their login.
  -B, --base branch             Change the base branch for this pull request
  -b, --body string             Set the new body.
  -F, --body-file file          Read body text from file (use "-" to read from standard input)
  -m, --milestone name          Edit the milestone the pull request belongs to by name
      --remove-assignee login   Remove assigned users by their login. Use "@me" to unassign yourself.
      --remove-label name       Remove labels by name
      --remove-milestone        Remove the milestone association from the pull request
      --remove-project title    Remove the pull request from projects by title
      --remove-reviewer login   Remove reviewers by their login.
  -t, --title string            Set the new title.

[isaquebc]

I have success using this command from DeepSeek.

gh pr ready ${BRANCH_NAME} --undo

The REST API still not working, but in this way I can convert it to draft.