docs: document infrastructure workflows and VS Code tooling#6
Conversation
README was missing agentics-maintenance.yml, copilot-setup-steps.yml, and the .vscode/ directory from the repository layout section. Added an "Infrastructure workflows" table explaining how these files are created and what they do, so contributors aren't confused by files absent from the documented workflow table. CONTRIBUTING.md now explains what .vscode/mcp.json and settings.json provide for VS Code + GitHub Copilot Agent users. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
/repo-assist fix the conflict |
|
✓ Repo Assist completed successfully, see workflow run. |
This comment has been minimized.
This comment has been minimized.
|
/repo-assist rebase this branch onto origin/main, resolve the README.md conflict by keeping all three file-layout lines (weekly-research, agentics-maintenance.yml, copilot-setup-steps.yml), and push the rebased branch with force-with-lease to update this PR. Do not just write a comment — actually push the commits via push-to-pull-request-branch. |
|
✓ Repo Assist completed successfully, see workflow run. |
|
Warning The 🤖 This is an automated response from Repo Assist. Done — the branch has been rebased onto Conflict resolution: the The PR should now merge cleanly.
|
Two workflow files and the .vscode/ directory existed but were absent from all documentation — a contributor scanning .github/workflows/ saw 9 files while the README only accounted for 7. README.md: - Add agentics-maintenance.yml and copilot-setup-steps.yml to the repository layout code block with inline comments - Add .vscode/ directory (mcp.json, settings.json) to the layout - Add "Infrastructure workflows" section explaining both files: agentics-maintenance.yml is auto-generated (do not edit by hand); copilot-setup-steps.yml pre-installs gh-aw for Copilot Agent sessions CONTRIBUTING.md: - Add "VS Code + GitHub Copilot" subsection under Development setup describing what .vscode/mcp.json and .vscode/settings.json provide and that they activate automatically (no manual steps) Supersedes PR #6, which carried the same changes but accumulated merge conflicts as PRs #8–#15 landed on main. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Closing as stale. Opened 2026-04-19; since then README and CONTRIBUTING have been rewritten twice ( |
Four gaps caught by the end-to-end audit against this repo, the playground, and the prior agentfolio trial-memory notes: 1. Add 'workflow' scope preflight to both install skills. Default 'gh auth login' lacks the workflow scope, so the user's first 'git push' of a .lock.yml fails with "refusing to allow an OAuth App to create or update workflow without 'workflow' scope". Agentfolio memory flagged this gotcha; the plugin never checked for it until now. Fix: 'gh auth refresh -s workflow -h github.com'. 2. Stale "Every push to main" claim on update-docs in README.md and CONTRIBUTING.md. update-docs switched to 'schedule: daily' in d4295cf earlier today. Also cleaned up a stale pr-nitpick-reviewer reference in CONTRIBUTING (we removed it from dogfooding in b3f6341). 3. Strengthen the 'claude setup-token' TTY warning in auth.md. The command opens a browser auth flow and silently hangs in headless containers, SSH without forwarding, and the Claude Code REPL itself. New note: run it on a local laptop, paste the token into 'gh secret set' (which doesn't need a browser) elsewhere. 4. Fix reviewer-agent pipeline-summary run-id lookup. Instruction said 'gh run list --workflow=<name>.yml' but the actual files are <name>.lock.yml. Switched to --workflow="<Display Name>" form, which is more stable (file names could change; display names are human-authored). Caught before the audit caused a real user to trip, but flagging: (2) and (3) directly, (1) inherited from the author's own past agentfolio session (the dev environment's privileged setup masked it from the dogfood), (4) degraded silently in dogfood #6 without anyone noticing.
What
Two workflow files (
agentics-maintenance.yml,copilot-setup-steps.yml) and the.vscode/directory were present in the repository but absent from all documentation. A contributor scanning.github/workflows/would find 8 files but the README only accounts for 6 — a confusing gap.Changes
README.mdagentics-maintenance.ymlandcopilot-setup-steps.ymlto the repository layout code block with inline comments.vscode/directory to the layout with comments formcp.jsonandsettings.jsonagentics-maintenance.ymlCONTRIBUTING.md.vscode/mcp.jsonand.vscode/settings.jsonprovide and that they require no manual activationWhy
Documentation gaps are treated like failing tests. These files exist, serve distinct purposes, and affect the contributor experience — particularly:
agentics-maintenance.ymlis auto-generated and silently reverts if regenerated; contributors need to know not to edit itcopilot-setup-steps.ymlis only useful if contributors know it exists.vscode/config provides zero-config MCP tooling for VS Code + Copilot users but was invisible without this noteTesting