Will the copilot always run after every commit to origin?

[Rod-at-DOH]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Copilot in GitHub

Body

I'm reading through the GitHub Copilot documentation pages, learning more about how to use this fascinating new tool! Right now, I'm reading through the pages dealing with .github/copilot-instructions.md. Very interesting, but some details are left out so I'm asking here.

First, I conclude that the GitHub Copilots will run after every commit to the remote repo. Am I correct about that?

Second, assuming the answer to my first question is yes, then how can I prevent that from happening after every push to remote? When I am working alone, I tend to perform frequent commits to my local repo and then pushes to remote. I do this so that I have a clear view of how my thinking has progressed over time. But I don't want every push to remote to trigger Copilot to run. That would just burn through my tokens quicker than I care for that to happen.

[Bielcx]

Great questions! Let me clarify both points:

1. Does GitHub Copilot run after every commit?

No, not exactly. GitHub Copilot doesn't automatically trigger on every commit. The .github/copilot-instructions.md file serves as a configuration file for Copilot's behavior when YOU use it in your IDE/editor, not as an automated trigger that runs on commits.

Copilot runs when:

You're actively using it in your code editor (VS Code, JetBrains, etc.)
You invoke it manually or let it suggest completions
You're in a GitHub Codespaces environment

It does NOT run automatically on every push to remote as a CI/CD action.

2. Preventing unnecessary token usage

Since Copilot doesn't auto-trigger on commits, you can control usage by:

In your IDE:

Disable Copilot when you're doing frequent local commits
Toggle it on/off per file or project via settings
Use keyboard shortcuts to enable/disable as needed

For GitHub Codespaces:

Disable Copilot in Codespaces settings if you want to preserve tokens
Settings → Copilot → toggle off

GitHub Copilot for Enterprises:

If using enterprise licenses, token usage is typically monthly
Check your organization's consumption dashboard
Pro tip for your workflow:

If you're worried about token burn-through, you can:

Enable Copilot only when you need significant help
Use local commits frequently without it enabled
Push to remote without Copilot active
Re-enable when you need AI assistance for complex problems

[Rod-at-DOH]

You're right and I knew the Copilot runs when I use it but forgot when I wrote my question. Thank you for reminding me of that.

However, you mentioned what I hadn't thought of or knew, and that is that Copilot can be involved when using what is free; code completion helps. That is something I didn't know, nor did it occur to me. That will make what is normally a free use of Copilot into something which charges/consumes tokens. I'm going to go over what you wrote here, so I can use it elsewhere. (My company has decided to not use GitHub Copilot. I am using the free version, but that leaves me with very little tokens to burn before I've run out of them.)

This makes me think of something I'd like to suggest. With GitHub Workflows, it is possible in the GitHub.com interface, to disable workflows. It's a bit obscure to find out, but it isn't hard and we use that pattern a lot. It would be nice to have something like that available in the .github/*.md files, etc. Where do I go to post that suggestion?

[Bielcx]

I totally understand ur concern about token consumption, especially with limited free-tier usage.

You're right that having a configuration option directly in .github/copilot-instructions.md (or a similar config file) to disable Copilot would be really useful. It mirrors the workflow disabling pattern you mentioned and would give developers more fine-grained control over their token usage.

To post this feat request, I'd recommend:

Head over to GitHub Community Discussions
Create a New Discussion under the "Ideas" category
Title it something like: "Feature Request: Disable Copilot via .github/copilot-instructions.md"
Explain your use case (limited tokens, wanting to control activation per project)
Reference the workflow disabling pattern as a precedent

The GitHub team actively monitors those discussions and considers community feedback for future features. Your suggestion has merit, especially for developers on free plans managing token budgets :)