beads/website
Scott Nixon 18f47fe8b6
docs: add GitHub Copilot integration guide with cross-platform MCP paths (#1348)
* fix(export): populate export_hashes after successful export (GH#1278)

Child issues created with --parent were missing from export_hashes table,
which affects integrity tracking and future incremental export features.

This fix ensures SetExportHash() is called for all exported issues:
- Updated ExportResult to include IssueContentHashes map
- Updated finalizeExport() to call SetExportHash() for each exported issue
- Updated exportToJSONLDeferred() to collect content hashes during export
- Updated performIncrementalExport() to collect content hashes for dirty issues
- Updated exportToJSONLWithStore() to call SetExportHash() after export
- Updated daemon's handleExport() to call SetExportHash() after export

Added test TestExportPopulatesExportHashes to verify the fix works for
both regular and hierarchical (child) issue IDs.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* docs: add GitHub Copilot integration guide

Add comprehensive documentation for using beads with GitHub Copilot in VS Code via the MCP server.

New files:
- docs/COPILOT_INTEGRATION.md - Complete setup guide with prerequisites, MCP tools reference, example workflows, troubleshooting, and FAQ
- website/docs/integrations/github-copilot.md - Shorter website version

Updated files:
- docs/INSTALLING.md - Added GitHub Copilot row to setup matrix and new "GitHub Copilot (VS Code)" section with quick setup steps
- website/docs/getting-started/ide-setup.md - Added GitHub Copilot section
- website/docs/integrations/mcp-server.md - Added VS Code / GitHub Copilot configuration examples for both .vscode/mcp.json and settings.json

Key clarifications:
- Beads is a system-wide CLI tool installed once, not cloned into projects
- The .beads/ directory only contains the issue database
- Added FAQ addressing "Do I need to clone beads?" explicitly

Fixes #148

* docs: add cross-platform paths for user-level VS Code MCP config

  Add Linux and Windows paths alongside macOS for the VS Code
  user-level MCP configuration. Users can now find the correct
  path for their platform in a simple table format.

  Paths by platform:
  - macOS: ~/Library/Application Support/Code/User/mcp.json
  - Linux: ~/.config/Code/User/mcp.json
  - Windows: %APPDATA%\Code\User\mcp.json

  Fixes #148

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-27 11:25:14 -08:00
..
docs docs: add GitHub Copilot integration guide with cross-platform MCP paths (#1348) 2026-01-27 11:25:14 -08:00
src/css feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00
static feat: update to use core tap for beads installation (#1261) 2026-01-24 17:11:21 -08:00
.gitignore feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00
bun.lock feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00
docusaurus.config.ts feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00
package-lock.json feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00
package.json feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00
README.md feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00
sidebars.ts feat: add Junie agent integration 2026-01-13 08:41:25 -06:00
tsconfig.json feat: add llms.txt standard support for AI agent discoverability (#784) 2025-12-30 18:27:50 -08:00

Beads Documentation Site