You have a GitHub repository that uses the GitHub Copilot coding agent to resolve issues and create draft pull requests. The repository has a ruleset named ruleset1 that enforces the following:
Signed commits
Branch protections that require status checks to pass before merge
The agent is blocked from operating in the repository because it fails to comply with the signed-commits rule.
You need to ensure that the agent can create and push changes to copilot/ branches. The solution must enforce the signed-commits rule for human developers on protected branches.
What should you do?
Suggested Answer: D
Explanation:
Adding Copilot as a bypass actor for the ruleset permits the coding agent to create and push its working changes without removing the signed-commit control for human developers. This is the narrowly scoped exception required by the scenario.
Making Copilot a repository owner grants excessive privilege and is not needed to resolve the signing restriction. Granting general push permission does not override a ruleset that blocks unsigned commits. Removing the signed-commit requirement weakens protection for every actor governed by the ruleset, including human developers on protected branches.
A bypass actor should be used deliberately and limited to the required automated identity and scope. The protected branch requirements, status checks, and human review processes should remain in place before agent-generated changes are merged.
Study-guide topics: rulesets, bypass actors, branch protection, and least-privilege exceptions.
===============