Better process tasks.before in gitpod.yml
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Currently, we defined before as
before: Use this for tasks that need to run beforeinitand beforecommand. For example, customize the terminal or install global project dependencies.
| Doc Image (source) |
|---|
![]() |
When user starts a workspace with prebuild and task only with before and command
- Prebuild will run
before(prebuild) - Workspace will load prebuild result
- Workspace will run
before(run) - Workspace will run
command(run)
But logs order is before(run) > before(prebuild) > command(run)
And that confused users
Proposal
- Do not run
beforeif there is noinitcommand in prebuild, this will makebeforemore like its define - Make the order of output assign to tasks exec order
Related Info
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 with the gitpod.yml task configuration and trace the execution path for before, init, and command during prebuild and workspace startup. Reproduce the log order described in the issue and inspect any existing tests for task execution. Done means before is skipped when the prebuild has no init command and output order matches execution order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100
