Skip to content

Move ports with descriptions to the top of the ports list #16253

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hobgoblina opened this issue Feb 6, 2023 · 5 comments
Closed

Move ports with descriptions to the top of the ports list #16253

hobgoblina opened this issue Feb 6, 2023 · 5 comments
Labels
editor: code (browser) editor: code (desktop) feature: ports meta: stale This issue/PR is stale and will be closed soon meta: 🤔 reporter-feedback-needed cannot process further since we need more info from the reporter team: IDE

Comments

@hobgoblina
Copy link

hobgoblina commented Feb 6, 2023

Objective

Would be nice to have ports with descriptions appear at the top of the ports list.

I provide descriptions for ports that users are likely to use, but there's a handful of other exposed ports that users are very likely to ignore, which I don't provide descriptions for. This makes it easy to find the useful ports, but they always appear at the bottom of the list... which, for some projects, means that they aren't visible unless you scroll down, which new gitpod users might not realize.

Screen Shot 2023-02-06 at 17 13 37

@hobgoblina
Copy link
Author

Quickly realized after creating this issue that this happened because I had set the easy-to-ignore ports with the following, which was defined above the useful ports in my .gitpod.yml.

- port: 3000-9229
    onOpen: ignore

Moved that to the bottom of the port definitions and now the ones with descriptions are at the top.

Leaving this open in case the original suggestion still sounds like a good idea to folks.

@akosyakov
Copy link
Member

akosyakov commented Feb 9, 2023

Ports are respecting order from .gitpod.yml by design. It is up to user to add them and reorder. I am not sure there is anything to do, maybe clarify docs?

@akosyakov akosyakov added the meta: 🤔 reporter-feedback-needed cannot process further since we need more info from the reporter label Feb 10, 2023
@loujaybee
Copy link
Member

loujaybee commented Feb 10, 2023

Thanks for raising @necropolina ! :) 👋 You might find this epic about ports useful or interesting: #9262. Also, here is a previous related issue with some context + additional discussion: #7764

Ports are respecting order from .gitpod.yml by design. It is up to user to add them and reorder. I am not sure there is anything to do, maybe clarify docs?

Indeed. However, I do think the current docs (https://www.gitpod.io/docs/configure/workspaces/ports#ports-ordering) do cover this, not sure where else we'd want to add. One thing we could do is do a better job of linting / offering best practices to users, and this could be one. For instance as part of something like: #12893. Maybe we could do this as part of work on inner loop: #7671. For now I will close until we have a more concrete idea of what fix we'd like to see 🙏

@akosyakov
Copy link
Member

@loujaybee 👍 for ability to guide. The ports view could allow to change order and automatically apply in .gitpod.yml.

@gtsiolis gtsiolis changed the title Feedback Issue: Move ports with descriptions to the top of the ports list Move ports with descriptions to the top of the ports list Mar 13, 2023
@stale
Copy link

stale bot commented Jun 11, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jun 11, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor: code (browser) editor: code (desktop) feature: ports meta: stale This issue/PR is stale and will be closed soon meta: 🤔 reporter-feedback-needed cannot process further since we need more info from the reporter team: IDE
Projects
None yet
Development

No branches or pull requests

5 participants