Feature Request: multiple default 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
Is your feature request related to a problem? Please describe
Enterprise customers having to gitpodify multiple repos that require the exact same or almost exact same config could do it more quickly by having a custom default gitpod.yml available.
Describe the behaviour you'd like
Having a custom set of gitpod.yml files, customers working with a big number of repositories could easily refer to them e.g. with one command when they need to gitpodify a repo. It would increase efficiency gitpodifying at a larger scale.
For them this could be either a template or a base that they could extend from.
Describe alternatives you've considered
Additional context
Signal(s) internal
https://github.com/gitpod-io/customers/issues/48
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
No source file, test, or entry point is identified in the issue. Start by clarifying how custom default gitpod.yml files should be stored, selected, and extended, using the linked customer signal as context; completion criteria are not yet defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100