An organization wants to let Copilot coding agent work on selected repository issues. The agent should be able to create implementation branches and draft pull requests, but repository maintainers must still review and merge the work through the normal pull request process. The repository already has branch protection on main, but Copilot coding agent has not yet been enabled. Which four actions should you perform in order? 1. Review the draft pull request and required checks 2. Create or select a clearly scoped implementation issue 3. Disable required reviews on the default branch 4. Enable Copilot coding agent for the repository 5. Merge the pull request before reviewing generated changes 6. Assign the scoped issue to Copilot

The correct sequence ensures the Copilot coding agent is properly configured and utilized within the existing workflow. First, enable Copilot coding agent for the repository (4) to grant it the necessary permissions and activate its functionality. Next, create or select a clearly scoped implementation issue (2). This provides the agent with a well-defined task, which is crucial for effective autonomous work. Then, assign the scoped issue to Copilot (6), instructing the agent to begin working on that specific task. Finally, review the draft pull request and required checks (1), as the agent will create a draft PR for review, aligning with the requirement that maintainers review and merge the work. Option "2 → 6 → 4 → 1" is incorrect because Copilot must be enabled before an issue can be assigned to it. Option "4 → 3 → 6 → 5" is incorrect because disabling required reviews (3) contradicts the requirement for maintainer review, and merging before reviewing (5) is a critical security and quality flaw. Option "6 → 2 → 1 → 4" is incorrect because Copilot cannot be assigned an issue (6) or create a PR (1) if it's not yet enabled (4).