Repository plugin defaults and enterprise plugin controls generally available
By Steven Van ·
Maintainers can set default plugins per repository, and GitHub Enterprise Cloud admins can require or block plugins for Copilot Business and Enterprise users.
Repository plugin defaults and enterprise-managed plugin controls are now generally available in VS Code, Copilot CLI and the GitHub Copilot app. GitHub's plugin documentation describes how the two layers fit together in GitHub Copilot.
Repository defaults
Trusted repositories can install and enable default plugins for contributors. A maintainer defines a plugin marketplace and default plugins once, so contributors don't have to repeat setup for each project. Defaults live in .github/copilot/settings.json.
Contributors can turn off repository defaults where policy permits. Repository defaults do not make a plugin mandatory, and they cannot enable a plugin that managed policy blocks or use a marketplace that policy disallows.
Enterprise controls
Enterprise administrators can supply approved marketplaces and, through managed settings, require or block plugins. They can also restrict installation to approved marketplaces.
- Required plugins are installed and enabled automatically, and users can't disable them.
- Managed settings take precedence over repository and personal choices.
- Managed settings can only require or block plugins. They cannot enable an optional plugin by default.
Availability
Repository defaults are available to individual Copilot users and to users with Copilot Business or Copilot Enterprise. Managed controls are available on GitHub Enterprise Cloud for users with Copilot Business or Copilot Enterprise licences issued by the enterprise or one of its organisations.
