Move config to `.gitpod` folder
Open
Nobody has claimed this yet.
meta: never-stale
type: feature request
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
As suggested here we should put the gitpod config below .gitpod. It will reduce the noise on the top level, as most setups use two config files (.gitpod.yml, .gitpod.Dockerfile).
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 the repository's .gitpod.yml and .gitpod.Dockerfile files and search for references to their current top-level paths. The work is done when the Gitpod configuration resides below .gitpod and all relevant references still resolve to the moved files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile, yaml
- Domain
- developer-experience, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100