Allow using the browser extension with two (or more) gitpod installations
Open
Nobody has claimed this yet.
component: browser-extension
meta: never-stale
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
With Gitpod Enterprise there might be many users who want to use gitpod for more than one gitpod installation (i.e. gitpod.io and their gitpod enterprise installation).
- We should allow to add 'additional' gitpod installations by URL.
- A gitpod installation should return all domains for which it understands context URLs, so the user doesn't have to configure it but can just fetch it from there.
- Also, we might want to alter the button label slightly, to signal the user where the workspace is going to be opened.
- For context urls supported by more than one gitpod installation a drop down button seems good.
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 browser extension's Gitpod installation and context-URL handling; no files or tests are named in the issue. Define the configuration and discovery flow for additional installations, then cover installation-specific labels and a selector when multiple installations support the same context URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100