[potiuk]

GitHub now lets the pull request creation cap count draft PRs. Before this, a user held to a cap could open any number of drafts. GitHub exposes this as an optional include_drafts boolean on the PATCH /repos/{owner}/{repo}/interaction-limits/pulls/creation-cap endpoint, which pr_creation_cap already calls.

This adds github.pull_requests.creation_cap.include_drafts:

github:
  pull_requests:
    creation_cap:
      enabled: true
      max_open_pull_requests: 5
      include_drafts: true

• Sent only when the cap is enabled.
• Omitted → left out of the payload, so a value set by hand in the repository settings is kept.
• Set in the previous .asf.yaml and dropped now → false is sent, so removing the key reverts it.

README updated; six unit tests added. pytest (165 passed) and pre-commit run --all-files are clean.

Sandbox test against potiuk/infrastructure-asfyaml-sandbox at d537e97, verified by reading the creation-cap endpoint back after each run ({enabled, max_open_pull_requests, include_drafts}):

Row	Before	After	Run
Set (noop)	{false,7,false}	unchanged	run
Set include_drafts: true	{false,7,false}	{true,3,true}	run
Update to false	{true,3,true}	{true,3,false}	run
Key omitted, true set by hand	{true,3,true}	{true,4,true}	run
enabled: false	{true,4,true}	{false,4,true}	run

Not covered in the sandbox: the "key removed after it was set" path, because the previous .asf.yaml cache doesn't exist outside production. Unit tests cover it. The sandbox was reset to baseline afterwards.

🤖 Generated with Claude Code