A team has three repositories: web-portal, billing-api, and shared-libs. A developer wants Copilot coding agent to work only in billing-api, even though the issue mentions package names that also exist in shared-libs. Which option best scopes the agent to the intended repository? Select one answer.

Assigning Copilot from an issue within the billing-api repository is the most effective way to scope the agent. Copilot's context is primarily derived from the repository where it is invoked. By starting from a billing-api issue, you explicitly direct Copilot to focus on that repository's codebase, even if similar package names exist elsewhere. This ensures the agent prioritizes the relevant files and dependencies within billing-api. Creating an organization-wide planning issue is too broad and won't effectively scope the agent to a single repository. Adding all repository names to the issue would confuse Copilot by providing conflicting contexts. Starting from the shared-libs dependency graph would incorrectly direct Copilot's focus away from the intended billing-api repository.