You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
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
The text was updated successfully, but these errors were encountered: