Trigger Prebuild only when certain files or directories change
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
I'm actually super surprised I didn't find this when searching through the issues.
Triggering a prebuild on every commit can be very heavy. It might help Gitpod's backend infrastructure if users could specify directories and files that can be modified without triggering a prebuild. This is common in CI tools (see Gitlab's rules:changes ). For example, I would specify that changes to the README.md file would not trigger a prebuild.
Describe the behaviour you'd like
Use syntax similar to GitLab CI rules:changes to include or exclude files or directories from triggering prebuilds.
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 locating Gitpod's prebuild trigger entry point and the existing tests around prebuild scheduling; the issue does not name specific files. Compare the current trigger behavior with GitLab's rules:changes semantics, then define how configured file and directory changes determine whether a prebuild runs. Done means the configuration behavior is documented and covered by tests for included, excluded, and unrelated changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100