top of page

GitHub Copilot - Notes: Spaces

What is Copilot Spaces:

  • A dedicated Copilot chat with curated context

  • Uses selected:

    • Files

    • Issues

    • Pull requests

    • Custom instructions

  • More focused than general Copilot Chat


Key Difference vs Copilot Chat:

  • Copilot Chat → broad, general suggestions

  • Spaces → focused, context-driven responses


Why Spaces Improve Quality:

  • Narrow context → more accurate and consistent answers

  • Better for repeatable and domain-specific tasks


Setting Context:


Attach Files:

  • Add code, docs, configs, datasets

  • Uses repo default branch (auto-updated)

Add Instructions:

  • Define:

    • Goals

    • Style

    • Expected output

  • Keep instructions:

    • Clear

    • Short

    • Actionable

Context Order:

  • Most important files/instructions first

  • Improves response accuracy


When to Use Spaces:

  • When you need:

    • Consistent outputs

    • Reproducible results

    • Domain-specific answers

Examples:

  • Specific project/service

  • Runbooks or workflows

  • Known datasets


Best Practices:

  • Keep Space small and focused

  • Provide clear instructions + examples

  • Be mindful of context limits

  • Update context as needed


Exam Tip Summary:

  • Spaces = focused Copilot with curated context

  • Improves accuracy, consistency, reproducibility

  • Use for specific tasks, not broad exploration

  • Key elements:

    • Files + instructions

    • Context order matters

    • Keep it concise and targeted

Creating Your First Copilot Space


Creating a Space:

  • Go to: github.com/copilot/spaces → Click Create space

  • Add:

    • Name (clear and descriptive)

    • Owner:

      • Personal

      • Organization (shared access)

    • Optional description (for users, not AI)

  • Click Save


Ownership:

  • Personal Space:

    • Private use

  • Organization Space:

    • Shared with team

    • Uses GitHub permissions


Adding Context:

  1. Instructions

    • Free text to guide Copilot

    • Define:

      • Goals

      • Tasks

      • What to avoid

    • Improves relevance of responses

  2. Attachments

    • Provide supporting context


Types:

  • Files/folders (code, docs)

  • Issues and pull requests (via links)

  • Uploaded files (local)

  • Free-text content (notes, transcripts)

  • Always uses latest version from repo default branch


Key Idea:

  • Better organization + clear context

    → better Copilot responses


Best Practices:

  • Use clear, descriptive names

  • Keep instructions focused

  • Add only relevant context

  • Structure content logically


Exam Tip Summary:

  • Space = reusable, context-driven workspace

  • Steps:

    • Create → Name → Choose owner → Add context → Save

  • Context types:

    • Instructions + Attachments

  • Organization Spaces = shared collaboration

  • Quality depends on clarity and structure of context


Sharing, Discoverability, and Governance


Visibility and Sharing:

  • Set visibility:

    • Personal (private)

    • Organization (shared)

  • Share via link or org browsing

  • Use:

    • Clear title

    • Short description (purpose, audience, output)


Security and Access:

  • Uses existing GitHub permissions

  • No new access is granted

  • Users only see content they’re allowed to access

Best Practice:

  • Avoid sensitive data in text

  • Prefer linking secure, version-controlled files


Versioning and Freshness:

  • Spaces use live data from default branch

  • Issues/PRs update automatically

  • Keeps content current

If needed:

  • Add specific examples or snapshots manually


Governance:

  • Assign an owner

  • Add “How to use this Space” instructions

  • Include 1–3 example outputs

  • Keep “one job per Space”


Discoverability:

  • Use clear naming conventions

  • Add keywords in description

  • Share/catalog within organization


Best Practices:

  • Keep Spaces small and focused

  • Review regularly (monthly or per release)

  • Update:

    • Links

    • Examples

    • Instructions

  • Remove outdated or irrelevant content


Exam Tip Summary:

  • Spaces must be:

    • Easy to find

    • Secure to share

    • Well maintained

  • Key concepts:

    • Visibility (personal vs org)

    • GitHub permissions control access

    • Live data keeps Spaces fresh

    • Governance = ownership + review + structure

  • Rule:

    → One Space = one clear purpose

Do’s and Don’ts of Working in a Copilot Space


Do’s:

  • Keep questions tightly scoped to attached sources

  • Focus on one task or domain per Space

  • Use clear, structured prompts with constraints

  • Ask for:

    • Executable code

    • Queries/commands

    • References to sources

  • Provide:

    • Examples (1–3 high-quality)

    • Clear instructions

  • Iterate:

    • Refine prompts

    • Remove irrelevant context

  • Keep context:

    • Fresh (linked to repo)

    • Well-ordered (important first)


Don’ts:

  • Don’t @mention users or extensions

  • Don’t expect access to external/unattached content

  • Don’t overload Space with too much context

  • Don’t mix multiple use cases in one Space

  • Don’t paste sensitive data in free text


Best Practice:

  • If quality drops:

    → Reduce context or split into smaller Spaces


Exam Tip Summary:

  • Spaces work best when:

    • Focused

    • Context-driven

    • Well-structured

  • Key rules:

    • One Space = one purpose

    • Use examples + constraints

    • Keep context clean, relevant, and secure


 
 
bottom of page