this post was submitted on 20 Aug 2024
8 points (90.0% liked)

Linux 101 stuff. Questions are encouraged, noobs are welcome!

1026 readers
1 users here now

Linux introductions, tips and tutorials. Questions are encouraged. Any distro, any platform! Explicitly noob-friendly.

founded 1 year ago
MODERATORS
[email protected]
[email protected]
8
Best practices for organizing personal git repositories in /home folder? (slrpnk.net)
submitted 3 weeks ago by [email protected] to c/[email protected]
6 comments fedilink hide all child comments
 

There’s a lot of detailed information if you’re dealing with running a git server (/srv/git) or dealing with development (follow your company’s policies), reams of information about how to organize files inside a repository, and some apps will handle their own repository location (chezmoi), but not much about just keeping your personal git repositories organized without cluttering up your home folder:

  • a lot of Youtube videos are just grabbing a couple files so end up cloning into ~/Downloads and cleaning up later
  • GitHub and GitLab tutorials just mention clone into the folder of your choice
  • Codeberg’s “Your First Repository” has you cloning into ~/repositories
  • so, what have you found to be the cleanest/simplest/most comfortable?
    • “top-level” folder like ~/repositories or ~/repos ?
    • move down a level like ~/Documents/repos ?
      • (make use of an unused XDG folder like ~/Public ? (doesn’t seem likely))
    • something else that everyone adopted ages ago ?
top 6 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 3 weeks ago

I've also noticed guides cluttering the downloads and home folders by cloning directly to them. My own work around is to make folder called git or github in my home folder. Then each repository gets its own folder within that.

[–] [email protected] 4 points 3 weeks ago

A git workspace is a folder with several git repositories inside of it that are related. You can have multiple workspaces. I have one for my personal code ~/code and one for my work code ~/w

There are tools to help you manage git workspaces, like https://github.com/orf/git-workspace or https://github.com/StreakyCobra/gws

[–] [email protected] 4 points 3 weeks ago* (last edited 3 weeks ago)

I have them in

  • ~/Documents/Source for things I just want to look through but not compile myself
  • ~/Documents/Code/(Language)/(Project) for things I code by myself
  • ~/Programs/(Project) for things I actually modify and plan to compile and use myself

If you're wondering why Documents? I guess that just sticked from windows and made kind of sense, not that the nesting matters anyway with zoxide

[–] [email protected] 4 points 3 weeks ago

I have ~/git for fit repos, and a dedicated ~/git/ext for repos I do not own, but have locally cloned for various reasons.

[–] [email protected] 2 points 3 weeks ago* (last edited 3 weeks ago)

I have

/home/(username)/projects/thirdparty

/home/(username)/projects/lab and

/home/(username)/temp.

[–] [email protected] 1 points 3 weeks ago

My setup looks like this:

~/Projects/project_name/repo_name/

I found, I'll usually have additional files which I don't want to check into the repo, so I can place them underneath project_name/ instead.
In particular, I'll also often have multiple repos associated with a given project.

Downside: I don't really have a good place for repos, which I clone just to compile the given software for personal usage. At this point, I have a ~/Projects/foreign/ folder for them. Although, I guess, it might make sense to have a folder in general for user-installed applications, where I could also have those repos.