Repository navigation
Build Interactive Vega Visualizations in Verso with PowerShell - #377
Merged
HeyItsGilbert merged 1 commit intoOct 15, 2026
Merged
Conversation
✅ Deploy Preview for powershellorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
HeyItsGilbert
added a commit
that referenced
this pull request
Nov 3, 2026
## Summary
```text
.github/
└── instructions/
└── articles.instructions.md # applyTo: content/articles/**/*.md
GLOSSARY.md # new: AI slop, vibe coded, off-topic pitch
```
Path-specific Copilot custom instructions, scoped to community article
submissions only (layers on top of the existing repo-wide
`.github/copilot-instructions.md`, which both review surfaces already
apply alongside it). Copilot checks three categories on every article
PR:
```text
review(diff)
if unsafe: destructive commands / credential harvesting / prompt injection / phishing links / CoC violations
comment(quote, category)
if AI slop: generic filler / no firsthand specificity / untested-looking code /
re-explained docs / listicle padding / no PR validation evidence
comment(quote, category)
if off-topic: thin PowerShell content relative to self-promotion
comment(quote, category)
always: one triage summary comment — "Needs maintainer safety review: <category>"
never: imply the PR is blocked or rejected — maintainer has final say
```
Built from:
- a grilling session settling scope, categories, and enforcement stance
(advisory-only, since Copilot code review can't block merges)
- the precedent in
[#265](#265 (comment)),
where "vibe coded"/off-topic pitch content was caught manually
- the last 9 accepted article PRs (#57–#377), which surfaced the
"Validation" section convention (tool versions, commands run, links
checked) as a concrete, checkable signal — now folded into the AI-slop
checklist
## Evidence
- `applyTo: "content/articles/**/*.md"` glob verified against the live
tree: matches 1,210 files, correctly including both article bodies and
`_index.md` listing pages (per explicit scoping call), no false matches
outside `content/articles/`.
- Frontmatter parses cleanly (`applyTo` is the only key, no YAML
errors).
- No permanent tests apply — this is a prose instructions file read by
GitHub's Copilot review surfaces, not executable code.
## Merge Danger
**Door:** Two-way — it's a markdown instructions file; edit or delete
anytime with no migration cost.
**Blast Radius:** Low. Only affects Copilot's own review comments on PRs
touching `content/articles/**/*.md`; no build, routing, or runtime
behavior changes. Worst case is a false-positive advisory comment, which
a maintainer can dismiss — Copilot has no merge/block authority.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
git diff --check upstream/main...HEADnpm run buildnpm run validate:articles