Post

I would imagine you give it strict acceptance instructions in your custom instruction file and guidance with examples for how to test.

Hopefully someone has already gone through the pain? Is there an MCP server for GitHub Actions yet? Otherwise I'm thinking Copilot could be instructed to call the GitHub CLI with a flow that pushes to a branch, triggers a workflow, checks the logs, etc.

I told it to start using the GitHub CLI, and it did. It would still be nice to have this more deeply integrated though, especially when it comes to watching workflow runs, instead of polling to then pull the logs, etc.

Might be easier to do that in Copilot on Github itself?

"on GitHub itself" - I've got VSCode with my local git clone, I don't want to do that elsewhere. Ideally I'd just do it from a single place, which I've been doing this morning by just asking Copilot to call the GitHub CLI to test the workflow and check for status and output

I mean, if you are relying on changes pushed to github, and on Github CI as source of truth for whether it works, it just seems easier to avoid local clone altogether, and let it keep working on problem even when you are offline. But that's just me.