Personally, to keep my documents like Inkscape files or LibreOffice documents separate from my code, I add a directory under my home directory called Development. There, I can do git clones to my heart’s content

What do you all do?

  • Luna@lemdro.idEnglish
    0·
    2 months ago

    ~/projects for things I made

    ~/git for things other people made

    • comfy@lemmy.ml
      0·
      2 months ago

      Thinking of the projects I work on, I don’t understand the value in categorizing by language, rather than theme (~/Development/Web/, ~/Development/Games/) or just the project folders right there.

      • mbirth@lemmy.ml
        0·
        2 months ago

        Yeah, everyone has to find their own way of organising, I guess. For me, there are too many different little projects that it would get messy throwing them all in one folder. And they’re so varied that I couldn’t think of one single “theme” or topic for most of them. Nothing I would remember a week later anyways.

  • muhq@discuss.tchncs.de
    0·
    2 months ago

    ~/code for everything I want to change/look at the source code.

    ~/.local/src for stuff I want to install locally from source.

  • r3dw4re [null/void]@hexbear.net
    0·
    2 months ago

    For my personal projects I use ~/dev/projects/

    For clones I use ~/dev/clones

    My audio engineering stuff is at ~/audio/{samples, plugins, projects, templates}

  • donio@lemmy.world
    0·
    2 months ago

    Any naming convention is fine as long as it’s meaningful to you. But it’s a good idea to keep your own repos separate from the random ones you clone from the internet.

  • Blaiz0r@lemmy.ml
    0·
    2 months ago

    I used to use ~/devbut for years now I use ~/Workspace becaue Eclipse made me do it

  • JustEnoughDucks@feddit.nl
    0·
    2 months ago

    ~/workspace/git

    That way I can also keep other stuff there.

    I have a Code, simulations, ECAD, and FreeCAD folder in there where projects or 1-offs are stored and when I want to bring them to git, I copy them over, play around in the project folders again, then copy changes over when I am ready to commit.

    I could better use branching and checking out in git, but large mechanical assemblies work badly on git.