Cannot run scripts.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Cannot run scripts. If I add a new script to the GitHub Copilot app for a given project, it fails to run because my command is an alias defined in my ~/.zshrc
/bin/sh: foobar: command not found
But within that same terminal session, if I then try entering that alias on my own, it works. So it seems like there's some sort of race condition or something around using the default shell vs interactive shell.
| Field | Value |
|---|---|
| App version | 1.1.14 |
| OS | macOS 26.5.1 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
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 in the GitHub Copilot app from /chat with a script command defined as an alias in ~/.zshrc. Compare execution through /bin/sh with running the alias in the existing terminal session; done means the app can run that command reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, zsh
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100