Skip to main content

How to exclude specific content when using GitHub Copilot

GitHub Copilot is a powerful AI coding assistant and I couldn't miss it anymore. But there are times when you need to prevent it from accessing certain files or directories. Whether it's sensitive configuration files, proprietary code, or files that would add unnecessary noise to suggestions, exclusions help you maintain control over what Copilot sees.

Why exclude content?

You might want to exclude content from Copilot for several reasons:

  • Security and privacy: Keep API keys, passwords, and other secrets away from AI processing
  • Proprietary code: Protect sensitive business logic or algorithms
  • Noise reduction: Exclude generated files, dependencies, or build artifacts that don't help with suggestions
  • Performance: Reduce the context window size for faster suggestions

Reasons enough to spend some time configuring your content exclusions.

GitHub Copilot content exclusion settings

Content exclusion is a Copilot Business or Enterprise feature and can be configured at either repository-level or organization-level.

Repository-level exclusion

  • Navigate to your repository on GitHub
  • Go to Settings → Copilot
  • Add path patterns to exclude

Organization-level exclusion

Organization admins can set policies that apply across all repositories:

  • Go to your organization settings on GitHub
  • Navigate to Copilot settings

  • Configure content exclusion policies

 

These settings use glob patterns like:

  • **/secrets/** - Exclude all secrets directories
  • *.config - Exclude all config files
  • src/internal/** - Exclude internal source code

Sidenote: .aiignore file

The Jetbrains AI assistant supports the concept of an .aiignore file, similar to a .gitignore file.

I hope that we’ll see the same idea appear in VSCode when using Github Copilot.

More information

Content exclusion for GitHub Copilot - GitHub Docs

Excluding content from GitHub Copilot - GitHub Docs

Copilot content exclusion is now generally available in IDEs - GitHub Changelog

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more