Skip to content
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

Default Source Folder should sort repos based on "organization" #2263

Open
TCFox opened this issue Dec 15, 2024 · 0 comments
Open

Default Source Folder should sort repos based on "organization" #2263

TCFox opened this issue Dec 15, 2024 · 0 comments

Comments

@TCFox
Copy link

TCFox commented Dec 15, 2024

Currently, all repositories are cloned into the "Default Source Folder" by default. If two repositories have the same name but come from different organisations or different sources, the names will conflict (potentially other logic would come into play here, I haven't tried this). I find myself manually choosing a new directory to clone into every time to avoid this potential issue, sometimes requiring me to create a new source or organisation folder.

In repositories that are cloned using a GitHub, Gitea or other similarly known account, it would be awesome if repos could be instead cloned into a directory named after the organisation it belonged to (such as ~/DefaultSourceFolder/Organisation/Repository), rather than just directly in the Default Source Folder. This could be an optional toggle under the existing configuration option for the Default Source Folder.

Bonus points if we can also support the source as an additional nested folder, such that Github repos would default to ~/DefaultSourceFolder/github.com/organisation/Repository, with an additional toggle.

This would likely need to be limited to just connected accounts (OAuth, etc) with known functionality that supports organisations, as "organisations" aren't a native Git feature afaik. You would likely be unable to support arbitrary SSH/HTTP URLs, unless you opted to do some hostname matching for known cases such as ssh://[email protected]/..., but this will obviously be difficult for self-hosted Gitea or GitLab instances.

Thoughts? This would be an amazing feature to support for my use cases, and I imagine others might appreciate it also!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant