gitpod-io / gitpod-io/gitpod

Show pod status in IDE

Open
#7,477 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

aspect: performance component: gp cli component: local app editor: code (browser) editor: code (desktop) meta: never-stale team: IDE
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

I often work with many pods open, my interactions with them have unnecessary breaking context changes (lose train of thought / efficiency) and time wastes.

  • Checking to see if a pod is open yet is a breaking context change, and I lose time if I haven't noticed it is open yet (or has errored)
  • Jumping into a tab and scrolling to stop them timing out is a breaking context change (as I have no good warning that it is going to time out)
  • Waiting for a pod that timed out to restart is a breaking context change

Describe the behaviour you'd like

GitPods could use the titlebar, in particular the favicon to indicate gitpod status:

Lifecycle:

  • Pod starting
  • Building image
  • Start / Image build failed (error icon)
  • Pod active (normal gitpod icon)
  • Pod will timeout in 10 minutes (configurable)
  • Pod has timed out

This means when working in the browser I have an at a glance way to see the top level status of all my workspaces (in that browser).

Good favicons for each of these are hard to do. They need to indicate the status as well as the fact it is a gitpod (so as not to be confused with other tabs).

Describe alternatives you've considered

  • Using titlebar text

    • I'm unlikely to notice this, particularly if lots of tabs are open
  • Browser Notifications

    • I generally find these annoying, but they could be helpful in addition to the titlebar
  • Building my own alert system

    • Very involved
    • Requires adding things to image & gitpod.yaml & an external database/system

Additional context

None

Thanks guys

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 IDE's browser titlebar and favicon handling, then trace how workspace lifecycle states are exposed; done means the requested pod states are distinguishable at a glance without opening each workspace.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.