<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=339135) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Gitlab is one of the few git suites that offers a directory structure. As such, when working locally, I effectively mirror my slugs to match gitlab. I imagine that a fair amount of users do this, too, just because it keeps things pretty easy to compare. Because of this, what will happen sometimes is that I will actually navigate to gitlab instead of my local directories when attempting to open a project. I'm fully aware that technically that's just me creating confusion for myself, but I think a really nice feature would be to simply allow a user to "bind" a group/project to a local directory, and then simply open a particular application right there. For example, I often traverse my gitlab group as a directory. It would be really slick if there was simply a little icon button I could push which would allow me to open that project in my local directory via my default editor, VS Code in this case. #### A little app Due to how browsers works for local links, you would likely not be able to directly open a local folder directly for security reasons. A simple way around this would likely be a tiny application which the user would need to download, which they can then configure bindings for projects, and which application(s) to use for each one, likely with a default application and specific projects/groups getting a different application. So the flow would likely be something like: 1. User clicks "open locally" icon button on a project or group. 2. Application is launched, similar to how you can have links that open Zoom and whatnot. 3. If folder exists, application associated with that directory is opened at that local directory, a la `code /users/<user>/gitlab/<project>`. - If folder does not exist, user is prompted to bind an existing folder, or download the repo via a copy-pastable `git` command. <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. -->