You have a GitHub Enterprise repository that uses the GitHub Copilot coding agent and opens...

A properly configured branch ruleset establishes enforcement outside the agent’s editable task instructions. It can require pull requests, successful checks, and appropriate reviews before changes enter protected branches. In an enterprise setup, required workflows can also be governed centrally so that changing a repository-local workflow does not remove the organization’s validation requirement.

The ruleset must be configured to preserve the intended checks. Merely creating an empty ruleset does not solve the problem, and requiring a check whose implementation the agent can freely weaken is insufficient. Protecting workflow changes through required ownership review or centrally managed validation addresses that remaining gap. The agent should not receive bypass permission for these controls.

Option A increases authority rather than constraining the unwanted behavior. Option C removes the checks that are supposed to detect defective code. Option D affects treatment of untracked files and does not prevent changes to already tracked workflow definitions.

The control cannot guarantee successful reasoning, but it can prevent acceptance of a shortcut that defeats validation.

Relevant curriculum topics are blocking prohibited actions, enforcing independent controls, and correcting undesirable behavior identified through evaluation.