We should be able to do this via simple computation....but can we get AI involved in here 👀?

Testing issue, please ignore.

Similar to #79.

Did you know through the URL you can customise the editor, class and some other stuff?

Would be cool to be able to open a workspace through the raycast extension using these URL options.

You can see some of them here: https://github.com/gitpod-io/website/pull/3377/files

Have a play, maybe it could be integrated somehow? 😍

Problem to solve

The menubar icon is a nice feature, but could push away users from using the extension if it's always visible.

Raycast is also a keyboard-first kind of application which guides users to navigate through keyboard shortcuts, and more.

Proposal

Introduce an option in the extension settings that disables the menubar icon.

Support to do something like this via Raycast

Instead of using /b, /p etc. to scope the search filter I'd love for us to use a Dropdown instead as that's the pattern I see used the most often in Raycast extensions.

E.g. something along the lines of this the screenshow below. Keep in mind I only added the dropdown to show what I mean, I didn't actually implement the filtering so that's why the list stil shows branches, pull-requests, issues.

I don't have the me option in the list in this quick prototype, but I think it makes sense to add that too ☺️

When getting to this page where I can select branches, and issues. I almost found myself wanting to click an issue, to go re-read and re-familiarise with the GitHub issue, or PR, and didn't want to open a workspace straight away. Is there someway we could blend "open in GitHub" and "open a workspace" type actions together? 🤔

Cc @Palanikannan1437 @henit-chobisa

Cc @mads-hartmann because we recently chatted about this

The input placeholder for the link to GitHub when setting up the extension means I have to re-write or remember the URL it as there's no easy way to copy paste or click the placeholder text. I would suggest:

• Make the input placeholder just look like a "real" access token, e.g. ghp_huMrY****************************
• Add a clickable link, or some easier flow to get redirected to GitHub for the token

This is personal preference: I'd remove the text "Before you can start"... etc, as it's implied by the page. Or, consider shortening the copy to be punchier / quicker? If possible could you put the "about this extension" below the input field, also? Feels like a lot of information that I'm required to read before I input the token? (just some other UI clean up thoughts, a little unrelated to the original issue, but thought I'd share if you make a change to that page 😁 !)

Can we reduce the number of steps to open a familiar repo? Possibly by moving some of the options from step 3 onto step 2, or maybe even into the main search page of Raycast? To open a repo I have to:

1. Type "Gitpod"
2. Select a repo
3. Select a context

Is there any way we could bring useful recent contexts to the 2nd, or even 1st page? So that I've got my "recently" used or most frequently used contexts more accessible? 💭 🤔

Step 1	Step 2	Step 3

Searching through branches can be easier to understand and use.

Cc @Palanikannan1437 @henit-chobisa

Cc @mads-hartmann because we recently chatted about this

Oh, there is not a .gitpod file. I can work on this to offer a workspace ready to use 😄

Cc @Palanikannan1437 @henit-chobisa

Cc @mads-hartmann because we recently chatted about this

Current Behaviour

Expected Behaviour
Change actions's text to match the respective context i.e. Branches/ PRs and Issues

The section needs to be hidden.

Should be able to open all the template repositories from "gitpod-samples" for users to simply prototype faster!

Description

Along with Recently visited repositories, showing Recent CONTEXTS would be helpful for faster access

Existing Behaviour

Shows recently visited repositories

Why?

The current behaviour results in bad DX, incase the user wants to open a particular context repetitively while working on a particular branch!

Currently though things are cached, things still don't seem "instant" enough for me. I want this to be blazing fast 🙃.

Might consider moving from the default caching Raycast provides to something like React-query for more fine grained control while improving the search recommendations from GitHub tailored towards the user.

I want to get to the place I want, as fast as I could.

I would like to propose a way to change the configuration of the extension.

The most important thing I would like to change is Gitpod's endpoint: for Gitpod Dedicated and for some still running self-hosted installations, the host differs. For example https://github.com/gitpod-io/browser-extension allows for change of Gitpod URL.

I have a repo for testing various aspects of Gitpod, including weird characters in branch names. It looks like when I try to open a branch like the ones listed below, it errors out.

I think this has caused more confusion than help, but is there any real value from having this org?

Cc @Palanikannan1437 @henit-chobisa

Cc @mads-hartmann because we recently chatted about this

I think this has caused more confusion than help, but is there any real value from keeping develop as the default branch?

Cc @henit-chobisa @Palanikannan1437

Cc @mads-hartmann because we recently chatted about this

Seems like the app figures out branches I own, or am working on (awesome!) could we also include the default or main branch there to simply start a workspace from the main branch? 💭 🤔

The GitHub Context suggestions needs a revamp on getting user's most relevant Branches (recents), Pull Requests (one with most comments of yours, the ones requested your reviews, etc) and Issues (the ones you've subscribed to, comments, etc) i.e. suggestions...

Another suggest, add an access to the gitpod variables page 😄

How about some VIM support building upon @axonasif's https://github.com/axonasif/dotsh configuration steps 🚀

Let's keep the most recent used repository at the top in the happy path.

Cc @Palanikannan1437 @henit-chobisa

Cc @mads-hartmann because we recently chatted about this

Problem to solve

Currently, users are left in blank after creating a workspace, either in an outdated workspaces list or having to make more actions to open the workspace.

Proposal

Redirect to VS Code Web, VS Code Desktop or the Terminal after creating the workspace and close the Raycast dialog.

Hi,

It would be great to integrate GitLab in this extension, I have more projects on GitLab than GitHub 🦊 😄

Building upon https://github.com/gitpod-io/gitpod-qa, we could plan on adding an extra convenience layer via Raycast to search answers from the Gitpod docs!

Further possibilities: Link it to the discord qa section (in case the user wants to continue the discussion) by researching on Discord APIs to do the same!

I use safari for browsing (default browser) but prefer Chrome/Firefox for using Gitpod (safari just has too many inconveniences like asking for permission to paste everytime, asking for permission to open a link, etc)

Hence a global preference for Setting your Default browser for Gitpod would be awesome for my use case 🚀

Hello 👋
I would be interested to see information about workspaces as the list of actives, and why not to be able to remove a workspace 😄