A Copilot cloud agent task updates database migration code from an assigned issue. Copilot creates a draft pull request and the validation workflow fails on an integration test. The agent comments that the failure may require production-like database credentials. The repository requires CODEOWNERS review and passing required checks before merging. A developer wants to move the PR forward without losing the agent’s work. Which action should you take first? Select one answer.

Keeping the pull request in draft status allows the developer to continue working on the issue and address the integration test failure without prematurely signaling readiness for review. Requesting owner review at this stage is crucial because the agent identified a potential issue with production-like database credentials, which often requires input and approval from CODEOWNERS or security teams. This ensures that sensitive information is handled correctly and that the solution aligns with organizational policies before further development. Rerunning failed jobs with debug logging might provide more information, but it doesn't address the underlying credential issue. Converting the draft PR to ready is premature since the validation workflow failed. Adding credentials as repository variables might be part of the solution, but it should be done after consulting with CODEOWNERS to ensure security best practices are followed.