GitHub Copilot FAQ Cheat Sheet for Interviews (2027)
GitHub Copilot cheat sheet for DevOps and AI interviews: plans, agent mode, cloud agent, code review, custom instructions, content exclusion, risks.
GitHub Copilot is GitHub's AI assistant for writing, reviewing and changing code. It offers inline suggestions in the IDE, Copilot Chat, agent mode, a cloud agent that works on issues and opens pull requests, and code review. This cheat sheet gives 30 short answers DevOps and AI interviewers expect, plus tables and config snippets.
It is built for last-minute revision. For long-form answers grouped by level, use the main 80+ GitHub Copilot interview questions. Plan details were checked against GitHub Docs in November 2026 and change often, so confirm before quoting them.
Key takeaways
- Plans: Copilot Free, Pro, Pro+, Business and Enterprise. Free caps inline suggestions at 2,000 completions a month.
- Agent mode is available on Free and paid plans; the cloud agent (listed on GitHub's plans page as Copilot in the cloud) and full code review are paid features.
- Repository instructions go in
.github/copilot-instructions.md; path-specific instructions go in.github/instructions/*.instructions.mdwith anapplyToglob.AGENTS.mdfiles are also read. - Content exclusion is a Business and Enterprise feature and is not a security boundary.
- Every suggestion is untrusted input: review it, test it and scan it like code from a new contributor.
Cheat sheet tables
Plans at a glance
| Plan | For | Notes worth knowing |
|---|---|---|
| Copilot Free | Individuals trying Copilot | 2,000 completions a month, chat and agent mode with limits, review limited to selections in VS Code |
| Copilot Pro | Individual developers | Paid plan: cloud agent and full code review |
| Copilot Pro+ | Heavy individual use | Higher-priced individual plan; compare allowances on the plans page |
| Copilot Business | Organisations | Central seat management, policies, content exclusion |
| Copilot Enterprise | Enterprises on GitHub Enterprise Cloud | Business features plus enterprise-level controls |
Where Copilot works
| Surface | What it does |
|---|---|
| IDE (VS Code, Visual Studio, JetBrains, Xcode, Vim/Neovim, Eclipse) | Inline suggestions, chat, agent mode |
| GitHub.com | Chat, cloud agent on issues, code review on pull requests |
| GitHub Copilot CLI | Agentic help in the terminal |
| GitHub Copilot app | Chat and agent sessions away from the IDE |
Basics (1 to 10)
1. What is GitHub Copilot?
An AI coding assistant from GitHub that suggests code, answers questions about code, makes multi-file changes and reviews pull requests.
2. What is the difference between completions and chat?
Completions appear inline as you type. Chat is a conversation where you ask questions, request explanations or ask for changes.
3. What is agent mode?
A mode in the IDE where Copilot plans a task, edits several files, runs commands such as tests and iterates on errors, asking for approval where configured.
4. What is the Copilot cloud agent?
Often called the coding agent: you assign an issue or task, Copilot works in a cloud environment, pushes commits to a branch and opens a pull request for human review. It is a paid-plan feature.
5. What is Copilot code review?
Copilot reviews a pull request and leaves comments with suggested changes. Free users get only a "review selection" option in VS Code.
6. Does Copilot replace code review by people?
No. It adds a reviewer. Branch protection should still require human approval for production code.
7. Which languages does it handle?
Most mainstream languages and config formats, including YAML, HCL, Dockerfiles and shell. Quality depends on how much public code exists for the language and how clear your context is.
8. How do you get better suggestions?
Give context: open related files, write a descriptive comment or function signature, keep naming consistent and add repository instructions.
9. Can Copilot be wrong?
Yes. It can produce outdated APIs, insecure defaults or code that compiles but does the wrong thing. Treat output as a draft.
10. What is the monthly limit on Free?
GitHub's plans page lists 2,000 completions per month for Copilot Free, plus limited chat.
Configuration (11 to 17)
11. Where do repository custom instructions go?
In .github/copilot-instructions.md. Use it for build commands, coding standards and conventions Copilot should follow.
12. How do path-specific instructions work?
Create NAME.instructions.md files in .github/instructions with frontmatter that sets applyTo:
---
applyTo: "terraform/**/*.tf,**/*.tfvars"
---
Use the AWS provider version pinned in versions.tf.
Never hard-code credentials; read them from variables.
Run terraform fmt and terraform validate before proposing changes.
GitHub notes that on GitHub.com these are currently used by the cloud agent and code review; you can add excludeAgent to keep one of them from reading a file.
13. What is AGENTS.md?
An instructions file for agents. You can place several in a repository; the nearest one in the directory tree applies. GitHub also accepts a single CLAUDE.md or GEMINI.md at the root as an alternative.
14. What is content exclusion?
A Business and Enterprise setting that tells Copilot to ignore specific files: no suggestions in them, no use as context, and skipped in code review.
15. Is content exclusion a security control?
No. GitHub states it is not a filesystem security boundary; third-party MCP servers may not respect it, and IDEs may still pass semantic information indirectly. Protect secrets with access controls and secret management.
16. Who configures content exclusion?
Repository administrators for their repositories, and organization or enterprise owners for users who get Copilot through the organization.
17. How are seats and policies managed in a company?
Organization or enterprise owners assign seats and set policies, such as which features and models are allowed, in the Copilot settings for the organization or enterprise.
DevOps usage (18 to 24)
18. How is Copilot used for CI/CD?
Drafting GitHub Actions workflows, explaining failing jobs, writing test scaffolding and converting pipeline syntax between tools. Every generated workflow needs review of permissions and pinned action versions.
19. How is it used for infrastructure as code?
Generating Terraform modules, Kubernetes manifests and Helm values from a description. Validate with terraform validate, policy checks and a plan review before apply.
20. How do you stop Copilot from introducing secrets?
Instruct it never to hard-code credentials, enable secret scanning and push protection, and review diffs. Copilot can echo patterns from context, so keep secrets out of the repository.
21. What should a generated GitHub Actions workflow be checked for?
Least-privilege permissions, actions pinned to a full commit SHA or trusted version, no untrusted input interpolated into run steps, and secrets passed only where needed.
22. How does the cloud agent fit into a team workflow?
Assign small, well-described issues. The agent opens a pull request; CI runs; a human reviews, requests changes or merges. Write issues with acceptance criteria so the agent has a target.
23. How do you measure whether Copilot helps?
Use delivery measures you already trust, such as lead time, review time and change failure rate, alongside developer surveys, rather than counting accepted suggestions alone.
24. Can Copilot help with incident response?
It can explain logs, suggest queries and draft fixes, but the on-call engineer verifies every step. Never let generated commands run against production without review.
Risks and judgement (25 to 30)
25. What are the main risks?
Insecure or wrong code, outdated dependencies, licence questions for code resembling public code, over-trust by juniors and data exposure through prompts. Controls are review, testing, scanning and clear policies.
26. How do you handle insecure suggestions?
Run code scanning, dependency review and tests in CI on all pull requests, so AI-written and human-written code pass the same gates.
27. Should juniors use Copilot?
Yes, with guidance: ask it to explain code, write tests and compare approaches, and require them to explain any code they submit.
28. What does a good Copilot policy include?
Which plans and features are allowed, which repositories need content exclusion, review rules for AI-written changes, rules on secrets and personal data, and how to report problems.
29. How do you answer "Copilot generated a bug that reached production"?
Treat it like any defect: find which check should have caught it, add a test, tighten review or CI, and avoid blaming the tool or the person.
30. What is a strong closing answer about AI coding tools?
That they speed up drafting and exploration, while ownership, review and testing stay with the engineer, and that the team's existing quality gates apply to every change.
Prompting patterns interviewers like to hear
Many interviewers ask you to show how you would ask Copilot for help. Three patterns make good answers because they show you control scope and verify output.
State constraints up front
Name the versions, tools and rules the answer must respect. For example: "Write a GitHub Actions job that builds this Go service with the Go version in go.mod, sets permissions: contents: read, pins every action to a commit SHA and caches modules." Constraints stop the model from guessing defaults you would later have to fix.
Ask for a plan before code
For multi-file changes, ask agent mode to list the files it intends to change and why, then approve or adjust the plan. This keeps changes small enough to review and makes it obvious when the model misunderstood the task.
Ask it to test its own work
Request unit tests or a validation command alongside the change, such as terraform validate, kubectl apply --dry-run=server or the project's test target, and run them yourself. Then ask Copilot to explain any failure instead of accepting a second guess blindly.
Close the answer by saying you still read the diff line by line before committing.
Revision plan for the day before
- Re-read the plan table and the instruction file paths.
- Write one
.instructions.mdfile for a Terraform or Kubernetes folder from memory. - Review a generated GitHub Actions workflow and list what you would change.
- Prepare a 60-second answer on risks and controls.
For depth, continue with scenario-based Copilot questions, the Copilot preparation plan, most asked Copilot questions and Copilot benefits in DevOps automation. Our DevOps course covers GitHub Actions, Terraform and Kubernetes, with classroom batches in Kharadi, Pune and live online batches across India.
Frequently asked questions
What GitHub Copilot plans exist?
Copilot Free, Pro, Pro+, Business and Enterprise. GitHub's plans page also lists other options, so check it for the current set.
Is agent mode available on Copilot Free?
Yes. GitHub lists agent mode on Free and all paid plans, with usage limits on Free.
Where do Copilot custom instructions go?
Repository-wide instructions go in .github/copilot-instructions.md; path-specific ones go in .github/instructions as .instructions.md files with an applyTo glob.
Which plans support content exclusion?
Copilot Business and Copilot Enterprise.
Is content exclusion enough to protect secrets?
No. GitHub says it is not a security boundary. Keep secrets out of repositories and use access controls and secret scanning.
What does the Copilot cloud agent do?
It works on an assigned task in a cloud environment and opens a pull request for review. It requires a paid plan.
Can Copilot review pull requests?
Yes. Paid plans include Copilot code review on pull requests; Free offers only selection review in VS Code.
References
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0