Microsoft GH-600 - Developing in Agentic AI Systems

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.

===============

Statement

Answer

agent1 and agent2 jobs will run in parallel.

Yes

If the agent2 job fails, the workflow will fail.

Yes

GitHub Actions jobs run in parallel by default when no needs dependency establishes an execution order. Therefore, if agent1 and agent2 are independent jobs in the same workflow, they can begin concurrently when runners are available.

A job failure normally causes the workflow to be marked as failed. The workflow can be configured differently through conditional execution, continue-on-error, or dependent job logic, but no such exception is indicated here. An agent2 failure therefore results in a failed workflow outcome under standard behavior.

The environment: agent-sandbox setting identifies an environment associated with agent1. It does not itself create a dependency between agent1 and agent2, nor does it establish workspace isolation between them. Parallel execution requires separate coordination controls if both jobs can modify shared external resources or deploy to the same target.

Study-guide topics: parallel execution, job dependencies, workflow failure propagation, and execution environments. Reference: GitHub Actions—Workflow syntax .

===============