Allow prebuilds for specific branches
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
In the .gitpod.yml, we have the following option to enable prebuilds on all branches:
github:
prebuilds:
branches: true
I would like more granularity either through a regex, an array of branch names or a combination of the two.
Regex
github:
prebuilds:
branches: feature/*
Branch names
github:
prebuilds:
branches:
- main
- gp-code
Combination of regex & array
github:
prebuilds:
branches:
- main
- gp-code
- feature/*
A good use case is https://github.com/gitpod-io/openvscode-server. Prebuilds run for the main branch, but not gp-code. The repo has 263 branches, for all but main and gp-code we don't need 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
The issue identifies .gitpod.yml and the github.prebuilds.branches setting; start by tracing where this configuration is parsed and how branch prebuilds are selected. Done means supporting the requested branch names and patterns, including combinations, while preserving the existing true behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100