Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-03-13 04:35:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Aaron Powell
2026-02-26 16:33:14 +11:00
committed by GitHub
parent 0637cad186
commit d73c0bb1f3
7 changed files with 37 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
website/src/content/learning-hub/before-after-customization-examples.md
View File

@@ -16,8 +16,6 @@ relatedArticles:
- ./defining-custom-instructions.md
---
# Before/After Customization Examples
The power of GitHub Copilot customization becomes clear when you see concrete examples of how agents, skills, and instructions transform everyday development workflows. This article presents real-world scenarios showing the dramatic difference between default Copilot behavior and customized experiences that align with your team's standards, tools, and practices.
> Note: The following examples illustrate typical before-and-after scenarios. The actual before and after code may vary depending on the model used and any other context present at generation time.

4
website/src/content/learning-hub/copilot-configuration-basics.md
View File

@@ -364,11 +364,11 @@ A: Use the `excludedFiles` setting in your IDE configuration or create a workspa
**Q: Can I have different settings per project?**
A: Yes! Use workspace settings (`.vscode/settings.json`) for project-specific preferences that don't need to be shared, or use repository settings (`.github/copilot/`) for team-wide customizations that should be version-controlled.
A: Yes! Use workspace settings (`.vscode/settings.json`) for project-specific preferences that don't need to be shared, or use repository settings (for example, files in `.github/agents/`, `.github/skills/`, `.github/instructions/`, and `.github/copilot-instructions.md`) for team-wide customizations that should be version-controlled.
**Q: How do team settings override personal settings?**
A: Repository settings in `.github/copilot/` have the highest precedence, followed by workspace settings, then user settings. This means team-defined instructions and agents will apply even if your personal settings differ, ensuring consistency across the team.
A: Repository-level Copilot configuration (such as `.github/agents/`, `.github/skills/`, `.github/instructions/`, and `.github/copilot-instructions.md`) has the highest precedence, followed by workspace settings, then user settings. This means team-defined instructions and agents will apply even if your personal settings differ, ensuring consistency across the team.
**Q: Where should I put customizations that apply to all my projects?**

2
website/src/content/learning-hub/github-copilot-terminology-glossary.md
View File

@@ -14,8 +14,6 @@ relatedArticles:
- ./copilot-configuration-basics.md
---
# GitHub Copilot Terminology Glossary
New to GitHub Copilot customization? This glossary defines common terms you'll encounter while exploring agents, skills, instructions, and related concepts in the Awesome GitHub Copilot ecosystem.
Use this page as a quick reference when reading articles in the Learning Hub or browsing the repository.

2
website/src/content/learning-hub/understanding-copilot-context.md
View File

@@ -118,7 +118,7 @@ Using `#` to reference specific files gives Copilot precise context about which
GitHub Copilot has a maximum token limit for how much context it can process at once. When you have many files open or a long chat history, Copilot prioritizes:
1. **Closest proximity**: Code immediately surrounding your cursor
2. **Explicitly referenced files**: Files you @-mention in chat for CLI, and #-mention for IDE's (VS Code, Visual Studio, JetBrains, etc.)
2. **Explicitly referenced files**: Files you @-mention in chat for CLI, and #-mention for IDEs (VS Code, Visual Studio, JetBrains, etc.)
3. **Recently modified files**: Files you've edited recently
4. **Direct dependencies**: Files imported by your current file