You have a GitHub repository that uses a custom GitHub Copilot coding agent defined in...

Target

Correct selection

Checkout ref

${{ github.sha }}

File checked by test -f

github/agents/rollout-bot.agent.md

Profile passed to the deployment script

github/agents/rollout-bot.agent.md

The workflow must deploy an agent profile from a specific repository snapshot. Setting the checkout reference to ${{ github.sha }} identifies the commit associated with the workflow event, rather than following a branch reference that might move as new commits arrive. The checkout action supports selecting a commit SHA through its ref input.

Both subsequent operations must use .github/agents/rollout-bot.agent.md. The existence check confirms that the expected profile is present in the checked-out revision, and the deployment script receives that same version-controlled file. Using a different path would break the relationship between the validated profile and the deployed profile.

Rollback requires one additional operational distinction: reverting a change creates a new commit containing the restored content. The deployment must run against that revert commit. Re-running the original failed workflow run retains its original SHA and does not automatically deploy the later revert.

This approach keeps agent behavior, repository history, and deployment provenance aligned, making the profile’s effective version identifiable and recoverable.

Relevant curriculum topics are durable state, controlled rollback, and continuity of agent configuration across executions.