microsoft / microsoft/vscode-containers
Build and run task outputs do not get picked up by GitHub Copilot when attaching the last terminal command
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 87
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 9
Description
When interacting with Copilot you can attach the last terminal command as context. This is handy. However, it does not work for our CustomExecution based tasks--likely VSCode itself has no access to that output since it's in a pseudoterminal.
We may be able to execute them as subtasks.
Maybe upstream blocker: https://github.com/microsoft/vscode/issues/271391
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure when attaching the last terminal command from a CustomExecution-based build or run task. Read the linked upstream VS Code issue 271391 and trace how these tasks expose terminal output. Done means the relevant task output is available to GitHub Copilot, or the issue is confirmed blocked upstream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100