Set project root based on workspace context folder

[corneliusludmann]

When you open a workspace with a folder in the context URL like this one:

https://gitpod.io/#https://github.com/gitpod-io/gitpod/tree/main/components/ide/jetbrains/backend-plugin

We currently start the IDE with /workspace/gitpod as project root that has the folder components/ide/jetbrains/backend-plugin unfolded in the tree view. It would be even more useful when we change this behavior to open this folder as project root in the editor instead.

This would be a good step towards better support for projects inside mono-repos, especially when there are different languages in one repo. E.g. this would allow to better index a project in the JetBrains IDE.

(internal discussions)

Note: This issue is not about handling .gitpod.yml files in subfolders and should be handled in a separate issue.

---

Technically, we could check if

echo $GITPOD_WORKSPACE_CONTEXT | jq -r .isFile

is false and if this is the case set

echo "$GITPOD_REPO_ROOT/$(echo $GITPOD_WORKSPACE_CONTEXT | jq -r .path)"

as project root for the editor. Maybe there is even a more elegant way to do this, e.g using supervisor API resp. gp info instead of env vars (see also #6803 (comment)).

[akosyakov]

I don't oppose it, since current folder context is not really useful. What surprised me though today that I cannot change a folder in IntelliJ which what actually devs do while working on mono repos or just checking out another repo. I think we need to clarify with JetBrains whether it would be possible from client to open another project or folder. If not I guess we will need to think about the solution in supervisor frontend/ready screen to allow picking the folder. Or maybe it can be addressed when we go away from code with me to own protocol.

[corneliusludmann]

/schedule

[roboquat]

@corneliusludmann: Issue scheduled in the IDE team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[akosyakov]

I removed it, since I don't think @corneliusludmann have capacity to work on it anymore.

[loujaybee]

Relates to: https://youtrack.jetbrains.com/issue/CWM-4476

[stale]

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.

[ChristianHuff-DEV]

In regards of the "stale" tag: For me this is still an issue preventing me from using Goland.

[ChristianHuff-DEV]

Relates to: https://youtrack.jetbrains.com/issue/CWM-4476

Looks like the issue was resolved and released. Can you share an estimate when someone is gonna take another look at this?