Long story short: I’m starting on gamedev and want to get accustomed to version control without taking too much time learning about it

I know this is kinda asking to be spoonfed the answer, but truth is I don’t have a lot of free time and wish to focus mine on not losing interest in this new hobby (I know getting stuck on details and scope is one of the main pitfalls of new gamedevs). I also want to get used to do things the right way (otherwise I wouldn’t even be thinking about it this early) anywhere I can that isn’t too distracting from the goal. At least I’m contributing discussions to the community.

I know there are a few self hosted git options, but I don’t really understand much of what using git is like, technically I “learned” to use github for version control when doing a web dev course but I couldn’t keep a single part of that segment in long term memory.

I am looking for something I can host on my server and that I can push to from godot or a gui client (from linux). I am looking to selfhost partly for the giggles (if it’s somehow too complicated I’m willing to give up on that part) and partly because I don’t want to keep my stuff on someone else’s server if I can avoid it. I’m also trying to avoid having to learn about how to properly use it for as long as I can.

I think I’ve read about gitea on here before? I’d rather avoid ai-assisted projects because of the low commitment threshold to push updates, I’m pretty sure they’re more likely to give up with the updates than caffeine fueled coders thanks to the sunk cost fallacy.

I don’t plan on publishing anything on the time being, maybe after a while I might look into it more and use a proper service, one of my long term goals is making a foss game that people want to play, but that’s long down the road, I rather learn how to make games first.

  • Static_Rocket@lemmy.world
    link
    fedilink
    English
    arrow-up
    29
    ·
    edit-2
    8 hours ago

    This may sound terse, but I’m just trying to respect your time:

    1. You don’t need a server to start using git
    2. You don’t need a forge to host a git repository (gitweb works fine for indexing, reading, and cloning). Gitea, gitlab, forgejo, etc are all forges designed for full multiuser development with kaban boards, issue trackers, and CI pipelines.
    3. If you aren’t publishing anything then just play around locally with an IDE plugin for git or one of the listed GUIs https://git-scm.com/tools/guis

    If you ever do feel like publishing your work, it’s just a git remote add and git push away.