A Copilot coding agent opened a draft pull request for an assigned issue. The team expects tests to run immediately, but the integration environment should request approval only after the PR is ready for review. The repository owner sees this workflow run. Which option best explains the behaviour? Select one answer.

The integration-gate job is configured to run only when the pull request is not a draft (github.event.pullrequest.draft == false). Since the pull request is currently a draft, this job is skipped. However, branch protection requires both validate and integration-gate checks to pass before merging. Because integration-gate is skipped and thus hasn't reported a successful status, the merge is blocked, showing "expected — waiting for status to be reported." This aligns with the team's expectation that integration approval is only needed when the PR is ready for review (i.e., no longer a draft). The Copilot actor has sufficient permissions to open the PR and trigger the workflow. There's no indication of an environment reviewer rejecting deployment, as the integration-gate job, which would typically handle deployments or approvals, hasn't even run. The workflow trigger on: pullrequest with types: [synchronize] correctly processes commits pushed to the PR branch, including those from Copilot.