open-cli-tools / open-cli-tools/concurrently
Why doesn't `concurrently` use the shell it's being executed in?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.9k
- Forks
- 281
- Avg merge
- 17h 12m
- Merged PRs (30d)
- 1
Description
I'm trying to use concurrently to execute some bash functions in my shell that work fine when executed alone. However, they fail when being run with concurrently. After adding echo $0 to the functions, I realized that they're failing because concurrently is executing them with /bin/sh instead of bash.
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
The issue names no files, tests, or entry points. Reproduce a bash-function command through concurrently, then trace the relevant TypeScript CLI behavior; done means the invocation no longer forces /bin/sh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100