gitpod-io / gitpod-io/gitpod

Open workspace with files from a template context but no git remote

Open
#6,903 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

meta: never-stale team: webapp type: feature request
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

This is a revival of https://github.com/gitpod-io/gitpod/issues/86

Description

We would like to support opening archive URLs with Gitpod, e.g. like so:

https://gitpod.io/#https://github.com/gitpod-io/gitpod/archive/refs/heads/main.zip

This should give you a workspace containing all the files/directories from that archive, but no Git repository yet (i.e. no git init -- repository creation can then be done in a second step)

Use cases

Alternatives

  • Opening regular repositories in Gitpod, e.g. any one from https://www.gitpod.io/docs/quickstart; or some public repository; or a personal or private repository. This allows you to push changes if you already have access, or to create a fork if you don't have access, but creating brand new projects is inconvenient (you have to start by creating a repository yourself outside of Gitpod, as opposed to just starting to code in Gitpod and figuring out repo creation later on)
  • Another idea to allow starting from templates would be to make Gitpod create and initialize a new repository for you. This was initialliy proposed here: https://github.com/gitpod-io/gitpod/issues/5583

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation files or tests are named. Start by tracing how Gitpod handles the example archive URL, then verify that the resulting workspace contains the archive files without a Git repository or remote. Done means archive-based workspace creation works while regular repository opening remains unaffected.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, typescript
Domain
cloud, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.