You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Introduced native chat permissions mapping in cockpitWebviewSettingsHandler.
- Updated settings handling to sync native approval modes with VS Code configuration.
- Added experimental notice for GitHub integration in cockpitWebviewStrings and cockpitWebviewWorkspaceTabsMarkup.
- Expanded ApprovalBootstrapMode to include "default", "auto-approve", and "autopilot".
- Refactored syncApprovalMode function to streamline approval mode synchronization.
- Updated tests to reflect changes in approval mode defaults.
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ These are the default path and the main product surface.
109
109
110
110
`Todo Cockpit` is the planning and triage layer. A `Todo` stays a planning artifact: capture work, add comments, apply labels and workflow flags, and decide what should happen next.
111
111
112
-
OptionalGitHub inbox triage also lives here. The `Settings` tab can save repo-local GitHub repository settings plus a reusable automation prompt, then expose a cached GitHub inbox at the top of the board with `Issues`, `Pull Requests`, and `Security Alerts`. Refresh uses your existing VS Code GitHub sign-in, inbox rows can create a plain Todo or `Create Todo + Review`, and repeat imports reuse the existing GitHub-sourced card instead of creating duplicates. For setup, storage, and current limits, see [docs/github-integration.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/github-integration.md).
112
+
Optional, **experimental**GitHub inbox triage also lives here. The `Settings` tab can save repo-local GitHub repository settings plus a reusable automation prompt, then expose a cached GitHub inbox at the top of the board with `Issues`, `Pull Requests`, and `Security Alerts`. Refresh uses your existing VS Code GitHub sign-in, inbox rows can create a plain Todo or `Create Todo + Review`, and repeat imports reuse the existing GitHub-sourced card instead of creating duplicates. For setup, storage, current limits, and the road to stable, see [docs/github-integration.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/github-integration.md).
113
113
114
114
### Tasks
115
115
@@ -133,6 +133,10 @@ Research is especially useful when work should pull in fresher outside knowledge
133
133
134
134
These capabilities stay discoverable, but they are not required for the default path.
135
135
136
+
-**GitHub Integration** (experimental): repo-local inbox triage for issues, pull requests, and security alerts. Read-only, manual refresh, no mutation support yet. See [docs/github-integration.md](https://github.com/goodguy1963/Copilot-Cockpit/blob/main/docs/github-integration.md).
137
+
-**Telegram Notifications** (experimental): repo-local Stop hook that sends the last assistant reply to a Telegram bot.
138
+
-**Codex integration** (experimental): repo-local MCP, skills, todo coordination, and task-draft coordination for ChatGPT Codex in VS Code.
139
+
136
140
### Model And Agent Choice
137
141
138
142
Copilot Cockpit is designed for mixed-model work. Sometimes one model is better for planning, another for implementation, and another for research or code review. The goal is not to crown one universal expert, but to let specialized agents and model choices work together under one controlled workflow.
Copy file name to clipboardExpand all lines: docs/github-integration.md
+36-5Lines changed: 36 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
# GitHub Integration
2
2
3
-
Copilot Cockpit includes an optional repo-local GitHub integration for Todo Cockpit. It lets you save repository settings in the `Settings` tab, manually refresh a cached GitHub inbox, and turn GitHub items into Todo cards or review-oriented handoffs without exposing a runtime access token back to the webview.
3
+
> ⚠️ **Experimental** — This feature is experimental and may change or be removed in future versions.
4
+
5
+
Copilot Cockpit includes an optional, **experimental** repo-local GitHub integration for Todo Cockpit. It lets you save repository settings in the `Settings` tab, manually refresh a cached GitHub inbox, and turn GitHub items into Todo cards or review-oriented handoffs without exposing a runtime access token back to the webview.
4
6
5
7
This feature is intentionally narrow today:
6
8
@@ -147,12 +149,41 @@ That keeps the downstream task draft aligned with the earlier GitHub-aware revie
147
149
148
150
## Current Limits
149
151
150
-
- This is not a deep integration with the GitHub Pull Requests and Issues extension.
152
+
This integration is **experimental and read-only**. The following capabilities are not yet implemented:
153
+
154
+
### Not Yet Implemented
155
+
156
+
-**Bidirectional sync**: You cannot create, update, or close GitHub issues, pull requests, or alerts from Copilot Cockpit. The integration is strictly read-only.
157
+
-**Live push sync**: There is no webhook, event-driven, or polling-based automatic refresh. All inbox updates are manual.
158
+
-**Deep GitHub extension integration**: This does not integrate with the GitHub Pull Requests and Issues extension. It operates independently through direct REST API calls.
159
+
-**Issue/PR mutation**: You cannot comment on, assign, label, milestone, close, reopen, or merge GitHub items from within Cockpit.
160
+
-**Discussions**: GitHub Discussions are not fetched or displayed.
161
+
-**Workflow/actions visibility**: GitHub Actions workflow runs are not surfaced.
162
+
-**Review integration**: Pull request reviews, review comments, and review status are not fetched.
163
+
-**Notifications**: The GitHub notification inbox is not queried; only repository-scoped issues, PRs, and security alerts are fetched.
164
+
165
+
### Current Constraints
166
+
151
167
- Inbox sync is GitHub REST plus repo-local cached state.
152
-
-The sync path is read-only.
153
-
-Refresh is manual.
168
+
-Each lane is capped at 50 items and 2 pages per refresh.
169
+
-GitHub Enterprise refresh depends on VS Code's `github-enterprise` provider and a derivable server URI from `apiBaseUrl`.
154
170
- There is no webhook or live push sync.
155
-
- GitHub Enterprise refresh depends on VS Code's `github-enterprise` provider and a server URI that can be derived from the configured `apiBaseUrl` or is already configured in VS Code.
171
+
- Rate limiting can cause partial or failed refreshes.
172
+
- Only open issues and open pull requests are shown.
173
+
- Security alerts cover code scanning alerts and Dependabot alerts only; secret scanning alerts are not included.
174
+
175
+
## Road To Stable
176
+
177
+
For this feature to graduate from experimental to stable, the following would be needed:
178
+
179
+
1.**Bidirectional mutation support** — Create, update, and close issues/PRs from Todo Cockpit, with audit trail.
180
+
2.**Auto-refresh or webhook sync** — Optional polling interval or webhook receiver for live inbox updates.
181
+
3.**GitHub Pull Requests and Issues extension integration** — Optional deep linking or co-operation with the official extension.
"Konfigurieren Sie repository-lokale GitHub-Repository-Einstellungen, gecachte Inbox-Synchronisierung und einen wiederverwendbaren Automatisierungs-prompt, ohne das gespeicherte token an das Webview zurückzugeben.",
381
381
),
382
+
githubIntegrationExperimentalNotice: localize(
383
+
"This feature is experimental and may change or be removed in future versions.",
384
+
"この機能は実験的であり、将来のバージョンで変更または削除される可能性があります。",
385
+
"Diese Funktion ist experimentell und kann sich in zukünftigen Versionen ändern oder entfernt werden.",
0 commit comments