Skip to content

fix: remove unnecessary truncate comments from blog posts #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dfberry merged 1 commit into from
Jun 20, 2026
Merged

fix: remove unnecessary truncate comments from blog posts #67

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions website/blog/2026-06-08-copilot-config-files-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,6 @@ This guide is my attempt to create that mental model. I want to know what each f

*The folder-house metaphor emphasizes that these files live together, but each room has a different job.*

<!-- truncate -->

Those are the most commonly confused files. There are also `AGENTS.md` (an OpenAI/Anthropic agent convention — not a GitHub Copilot feature), hooks, and MCP configs.

## The Copilot Instructions File: Governance Layer
Expand Down
2 changes: 0 additions & 2 deletions website/blog/2026-06-20-squad-first-impressions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,6 @@ This post came from a coworker asking me, "Why Squad?"

![Watercolor illustration of a sunlit woodworking workshop with a team working on projects.](./media/2026-06-20-squad-first-impressions/2026-06-20-squad-first-impressions-watercolor-1-hero.png)

<!-- truncate -->

## Why Squad feels different from Copilot

Before Squad, my workflow was simple: open Copilot and ask one agent for everything. That works well for plenty of tasks, but it is still one perspective.
Expand Down