gitpod-io / gitpod-io/gitpod

Allow multiple scopes in env variables

Open
#12,877 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem? Please describe

Creating and managing enviroment variables with only one scope is hard, for example, I want to create env SECRET for repos under my user thisisommore and under my company lazarus which is only possible with *\* since lazarus/*,thisisommore/* is not possible and I will get this error if I try to do so
image

Describe the behaviour you'd like

I would like to use comma or some separator or some UI to create multiple scopes

Describe alternatives you've considered

Create two variables entries for each scope

Additional context

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 files, tests, or entry points are named. Start by locating the environment-variable scope validation and the UI or API that manages scopes, then trace how a single scope is stored and parsed. Done means one variable can target multiple repository scopes, including both the user's and company's repositories, with validation and management behavior covered.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.