GitHub Copilot setup and consulting

When do you need it?

• Your teams want to use GitHub Copilot, but it is unclear who gets a license and how.
• You need to decide which parts of your code stay closed to Copilot.
• You want to limit suggestions that match public code.
• Licenses are in place, but you cannot see who uses them and how much.
• You want Copilot’s answers and code reviews to follow your team’s rules.

What do we take on?

1. 1

   Setup and licenses

   We enable Copilot in your organization’s GitHub account and assign licenses by team. We track licenses that go unused for a long time.

2. 2

   Usage policies

   We agree with you which features and models are enabled. We also decide together whether to block suggestions that match public code.

3. 3

   Protecting your code

   We use content exclusion rules to close off files Copilot should not read. Configuration files that contain secrets are a typical example.

4. 4

   Fitting your team

   We add instruction files to your repositories that describe your coding rules. Copilot follows them in chat answers and code reviews.

5. 5

   Rollout

   We start with a small team. Based on usage data, we open Copilot to other teams step by step.

Copilot in code modernization

In our code modernization projects we also use GitHub Copilot to prepare repetitive changes. We describe this approach on the AI-assisted code modernization page.

Team training

On request, we give your teams hands-on GitHub Copilot training. We prepare the content around the languages and tools your team uses and its current level.

• AI-assisted code modernization
• Technical training

Frequently asked questions

What is GitHub Copilot?

GitHub Copilot is an AI assistant that suggests lines and functions as you write code. In a chat window it answers questions about the code and can review changes.

Does our code leave our network with Copilot?

To produce suggestions, Copilot sends the code context from the file you are working in to GitHub’s service. We use content exclusion rules to decide which files never enter that context. Where code cannot leave your environment, we work with models that run in-house.

Which license should we choose?

We choose the license type with you based on team size, the features you want and how your GitHub organization is set up. We recommend starting with a small team and expanding based on usage data.

How do you track usage?

We enable Copilot usage metrics and review regularly how much each team uses it. We identify licenses that go unused for a long time and recommend reassigning them.

Do you train our team?

Yes, we provide hands-on training on request. We prepare the content around the languages and tools your team uses and its current level.

Do you use Copilot in your own projects?

Yes, we use it in our code modernization projects. Every change Copilot prepares goes through a build, tests and review by our team.