118
Where Do You Guys Throw Your Local Git Repos?
(startrek.website)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I tend to follow this structure:
Is "code", "designs" and "wiki" here just some example files in the repo or are those sub-folders, and you only have the repo underneath
code
?They are the project's subfolders (outside of the Git repo):
code
contains the source code; version-controlled with Git.wiki
contains documentation and also version-controlled.designs
contains GIMP, Inkscape or Krita save files.This structure works for me since software projects involve more things than just the code, and you can add more subfolders according to your liking such as
notes
,pkgbuild
(for Arch Linux), orreleases
.Ah, interesting. In my current setup, I dump the auxilliary files into a folder above the repo, but it can certainly make it a bit messy to find the repo in there then...
I maintain a rule that all files above the repo must be inside a folder, with one exception: a README file. Including the
code
folder, this typically results in no more than 5 folders; the project folder itself is kept organized and uncluttered.