export declare const GITHUB_HELP = "# GitHub Integration\n\n- Include `issue_number`/`pr_number` and `--project` in your `memory-journal-mcp entry create` CLI command to auto-link\n- After closing issue/merging PR \u2192 create summary entry with learnings\n- CI failures \u2192 `actions-failure-digest` prompt or `memory://actions/recent`\n- Kanban: `get_kanban_board` \u2192 `add_kanban_item` / `move_kanban_item` / `delete_kanban_item` \u2192 document completion (project_number auto-resolves if repo is registered). **\u26A0\uFE0F Eventual Consistency:** GitHub Projects V2 read index is heavily eventually consistent. Do NOT rely on `get_kanban_board` to immediately reflect items that were just added or moved.\n- Milestones: `get_github_milestones` \u2192 track project progress, `memory://github/milestones`\n- Commits: `memory://commits/{project_number}/by-issue` and `memory://commits/{project_number}/by-pr` group commits by referenced issues/PRs.\n- Rate Limits & Status: Before expensive API operations, check `memory://github/status` (or `memory://github/status/{+repo}`) to inspect repository connectivity and status.\n- **Project Initialization**: To register a new project workspace, use the `register_project` (or `update_project`) MCP tool (`mj.admin.registerProject` / `mj.admin.updateProject` in Code Mode) or the `memory-journal-mcp project create <name> --path <path> --number <N>` CLI command.\n- **Multi-Project Routing**: If `memory://briefing` shows \"Registered Workspaces\":\n  - **Tools**: The `repo` parameter automatically resolves from `project_number`. If you omit both, they default to the primary project.\n  - **Resources**: Resource URIs like `memory://github/status` will fallback to the default project. To explicitly target another project, use the `{repo}` variant (e.g., `memory://github/status/{repo}`).\n  - **Dynamic Briefings**: You can explicitly request the briefing for a specific project by reading `memory://briefing/{repo}` instead of the global `memory://briefing` resource.\n\n## Copilot Review Patterns\n\nWhen the user has GitHub Copilot code review enabled:\n\n**Learn from reviews** \u2014 After a PR is merged or reviewed, use `get_copilot_reviews({ pr_number, owner, repo })` to read Copilot's findings (leave `owner` and `repo` empty to auto-detect from git). If patterns emerge (e.g., repeated null check warnings, missing error handling), suggest adding a rule or updating existing rules. Create journal entries tagged `copilot-finding` and link to the PR via `pr_number`.\n\n**Pre-emptive checking** \u2014 Before creating or modifying code, search journal entries with tag `copilot-finding` for patterns relevant to the current work. Apply those patterns proactively to reduce review cycles.\n\n## Available Tools\n\n- **Issues**: `get_github_issues`, `get_github_issue`, `create_github_issue_with_entry`, `close_github_issue_with_entry`\n- **Pull Requests**: `get_github_prs`, `get_github_pr`, `get_copilot_reviews`\n- **Context & Insights**: `get_github_context`, `get_repo_insights`\n- **Kanban**: `get_kanban_board`, `add_kanban_item`, `move_kanban_item`, `delete_kanban_item`\n- **Milestones**: `get_github_milestones`, `get_github_milestone`, `create_github_milestone`, `update_github_milestone`, `delete_github_milestone`\n\n";
//# sourceMappingURL=github.d.ts.map