copilot-tests.yml runs snapshot and verify against this repo, but no baseline is committed, so verify exits 0 with "No approved baseline" and nothing is enforced.
That is deliberate for adoption, since a repository should not have its first pull request blocked by a file nobody told it to create. But it means the integration is not dogfooded: we ship a pull-request gate for other people's repositories and do not run it on our own.
To close: commit .agentrust/copilot-baseline.json via python copilot/engine/capture.py approve, and add the action to a workflow on pull requests. Start with fail-on-drift: false if the baseline needs settling.
Worth noting this repo currently has none of the surfaces the check looks for: no .github/copilot-instructions.md, no .github/instructions/, no AGENTS.md, no skill roots. So the first baseline will be empty, and the gate's real value starts the moment someone adds one of those files, which is exactly the event worth catching.
copilot-tests.ymlrunssnapshotandverifyagainst this repo, but no baseline is committed, soverifyexits 0 with "No approved baseline" and nothing is enforced.That is deliberate for adoption, since a repository should not have its first pull request blocked by a file nobody told it to create. But it means the integration is not dogfooded: we ship a pull-request gate for other people's repositories and do not run it on our own.
To close: commit
.agentrust/copilot-baseline.jsonviapython copilot/engine/capture.py approve, and add the action to a workflow on pull requests. Start withfail-on-drift: falseif the baseline needs settling.Worth noting this repo currently has none of the surfaces the check looks for: no
.github/copilot-instructions.md, no.github/instructions/, noAGENTS.md, no skill roots. So the first baseline will be empty, and the gate's real value starts the moment someone adds one of those files, which is exactly the event worth catching.