Why do copilot initiated PRs require /check-enforcer override?

[jongio]

Whenever we assign an issue copilot it creates a PR and that PR hangs on check-enforcer. Can we figure out why? Right now we are having to repeatedly add /check-enforcer override to all of those PRs.

Example: #866 #878

[weshaggard]

Copilot doesn't have write access to our repo so checkenforcer which is a github workflow will not automatically trigger. So far I'm not aware of any way to work around this in the general case. However, for the mcp repo I'm actually thinking of retiring checkenforcer because it really isn't doing much for us so that will help eliminate this particular pain.

[weshaggard]

checkenforcer has been disabled now so this shouldn't be an issue in this repo any longer.