Epic: Re-use existing project scripts (Makefile, CI, Dockerfile)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
For most projects, they already have existing scripts for building/starting their projects [1]. Gitpod should be smart about detecting and re-using these scripts without forcing developers to re-write a new gitpod.yml file. We already have auto-detection for things like NPM commands, but we also should look at other configuration set up's like:
- CI configurations (GitHub actions workflows)
- Makefiles
- devcontainer.json [1]
- Existing Docker configurations
- Run/Debug configurations
There are two broad options (for the different configuration files):
- Directly integrate with the configurations, like the devcontainer standard [1]
- Map from these configurations to Gitpod configurations (either implicitly behind the scenes, or via explicit suggestion)
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 reviewing the proposed configuration sources: GitHub Actions workflows, Makefiles, devcontainer.json, Docker configurations, and Run/Debug configurations, along with the linked related issues. Determine whether the project should integrate these formats directly or map them to Gitpod configurations; done requires a decided scope and an agreed detection or reuse behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100