"Ignore" option for port on notification and in port management views
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Current notifications do not include an option to "ignore" the port (and persist to gitpod.yml) but this could be one of the more / most appropriate actions that a user wants to take. Currently the primary action is to make public. Would be good to review how we can add ignore behaviour into the initial notification (figure 1), and also into the various IDE port management views (figure 2). Similar to how we have "add to .gitpod.yml" in the extensions view (figure 3).
| Figure 1 | Figure 2 | Figure 3 |
|---|---|---|
![]() |
![]() |
![]() |
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
The issue identifies the port notification, IDE port management views, the extensions view pattern, and gitpod.yml as the relevant areas. Start by locating those UI entry points and the existing configuration persistence behavior. Done means users can choose to ignore a port from the notification and port management views, with that choice persisted to gitpod.yml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100


