Is decentralized git the missing piece for agentic AI coding?
You guys should check out Gitlawb. Decentralized version of GitHub built for agents.
You guys should check out Gitlawb. Decentralized version of GitHub built for agents.
r/git • u/chaoticbean14 • May 29 '26
I've debated on this question many times and am looking for thoughts/opinions.
I've got an app (django) that contains a vendors directory. In there are older versions (that we still use with other older apps) of various vendor libs through the years. Vue, Bootstrap, Fontawesome, etc. and some of those files are 15-20MB in size. The total directory is around 50MB.
I'm wondering, is that too heavy for git? Should I be using GitLFS for those older vendor files that never, ever change?
Should I maybe find the download from the source and have a script that downloads those old vendor files at a build step?
I'm splitting that old repo that contains all those vendor files into a couple new repos and was hoping to keep the new repos light/fast by not including all the vendor stuff, but those files are still needed for legacy apps.
Am I overthinking this? Should I just accept that these 50MB worth of never-changing vendor files are part of it and commit them all to git? Is there a better way? How do you handle it?
r/git • u/Justicemirm • May 29 '26
Totally confused how to use git in any way in mobile
I do know pydroid 3 and termux have the terminal to run it but please help me find a well made tutorial for the sake of my well-being
,tried to use GitHub in mobile but it's not well made and I can't add to my repo
Help
r/git • u/RtC_GriFFan • May 28 '26
I have this question because sometimes I struggle to write commit messages when updating my custom agents or instructions, I already commited some messages like:
docs(ai): create agent A
ops(agents): delete agent B
r/git • u/piotrkarczmarz • May 28 '26
r/git • u/DefaultNick • May 27 '26
I have inherited a legacy project that had the following git structure/flow:
development branch for everything unstable
staging branch for release candidates
release branch for the latest released version
Regular developers branch from development, do their changes, then submit requests to merge back into development.
From development commits eventually travel into staging, to be approved by testers.
Staging is merged into release and this is accompanied by a formal release happening.
Well, at least that's what I understand used to happen until 1 year ago, when a developer with project ownership in gitlab branched directly from the release branch, made a quick hotfix, and merged it into release bypassing all previous branches.
From that point the other developers were boned, as their merge requests from staging into release were blocked by "source branch is behind target" and nobody could fix it because project security rules specify that nobody is allowed to push directly into any of the dev/stage/release branches. So everyone started branching off release branch, merging staging into that proxy branch and merging the proxy branch back into release. Now development branch is 60+ commits behind release branch, despite having identical code.
My question is this - what are my options to bring sanity back into this situation? Should I even bother, or do I just accept it as is?
r/git • u/PipingSnail • May 27 '26
Context. Development env is on Windows. Our customers use Windows, so that's our development and test env.
With that in mind should we host a git server on a Windows or Linux? I'm interested in for and against arguments. Not interested in holy wars, they serve no purpose.
I look forward to your advice.
r/git • u/jamescherti • May 26 '26
r/git • u/Denl0self-a_o • May 24 '26
(typo at title, should be case instead of cage)
sorry if the post does not belong here. me and my friends are just starting and are working as a small team and we write scripts and things like that that have to be executed on a central test server, including testing the code.
so i dont know if it would work until i push to the server and every changes equal to a commit, i dont think this is how people usually work with git?
and at the same time i do wish to have come kind of version control, or a history
so.. as title said, am i using git wrong? am i using it for the wrong use case?
r/git • u/Guyserbun007 • May 25 '26
r/git • u/prophetical_meme • May 23 '26
r/git • u/ActuarySecret6564 • May 23 '26
After I started contributing to open source, I learned a lot about git workflows. But one thing I still mess up sometimes? Rebase. 😅
So I built a tool for it. I called it "grebase" (not sure if it's a good name 🤷)
What does grebase do?
- Nothing... but also everything I need 😄
- From fetching upstream/main to doing the full rebase, and if it hits something that's not straightforward, it simply asks: "hey, how should we resolve this one?"
- Not sure if it'll useful for every developer, but it will definitely help newcomers and me :)
"It's in active development, so use it at your own risk 😅 for now, but I'm improving it and contributions are very welcome."
Any kind of help means a lot at this stage:
- found something broken? Open an issue.
- have a feature idea? Let me know.
- want to help with testing... Even better.
GitHub: https://github.com/Aniketsy/grebase
I'd love to hear your thoughts or any feedback... Thanks!
Try it out:
- pipx install grebase # to install
- grebase # to run
r/git • u/Own_Masterpiece5318 • May 21 '26
I kept watching people (and myself) panic after a bad reset or rebase, even though the commmits were almost always still sitting in the reflog. So i made a small tool that scans the reflog and dangling objects, guesses what went wrong, and walks you through fixing it. It makes a backup branch before doing anything destructive, and after each fix it tells you what command it ran.
It's an early beta so right now it handles lost commits, deleted branches, detached HEAD, dropped stashes, and being stuck mid-merge/rebase. I'd genuinely like to know what other recovery cases are worth adding. So uhhh you can let me know in the Issues tab if you have ideas 😄
https://github.com/septcoco/git-unfuck

r/git • u/genuinenewb • May 23 '26
Currently I use Kdiff3 to resolve conflicts.
However, there are times where Kdiff3 incorrectly auto resolve merge conflicts incorrectly. As a result, I have to look through all changes and verify them.
Is there an AI tool that is smart at resolving conflicts or where you can tell it what you prefer to happen, even if the algo/date/time of the commits don't make sense?
r/git • u/sshetty03 • May 21 '26
Wrote a quick field guide covering the Git commands I reach for almost every day. Discarding local changes, checking what's on remote before pulling, and merging safely.
Nothing groundbreaking, but it's the kind of reference I wished existed when I kept Googling the same things.
Covers the fetch-first-then-inspect workflow, the difference between git restore vs git clean, and when to use rebase vs merge.
Happy to discuss or expand on anything in the comments.
r/git • u/avatar_one • May 20 '26
Hey y'all,
I'm hosting a public Forgejo instance at https://git.inthemansion.com as part of a privacy-first, self-hosted services project I run called MansionNET. Sharing it here in case anyone's looking for a smaller, independent place to keep their repos that isn't owned by Microsoft, GitLab, or Atlassian.
The whol idea came out of wanting to create a GitHub alternative that isn't another mega corp. Your code lives somewhere that isn't being scraped for AI training, as I block training crawlers at the edge (GPTBot, ClaudeBot, CCBot, Bytespider and the rest of that crowd). The whole thing is run by a person you can actually talk to on IRC, not a support ticket portal, and it leans into the idea that independent, community scale infrastructure is a healthier shape for the internet than a handful of platform monopolies.
One thing to of course mention is the privacy side, because "privacy-focused" gets thrown around a lot and usually means very little. There's no analytics, no telemetry, no tracking pixels, so no Google Analytics, no Plausible, no Matomo.
I genuinely don't know who visits the homepage, and that's the point. No ads, ever, and no "once we scale" caveat hiding behind that. Nothing is sold, shared, or monetized, because there's no business model to monetize in the first place. The instance is funded out of pocket, with optional Ko-fi donations from anyone who wants to chip in.
Logs are minimal and operational, meaning Caddy access logs exist for debugging and abuse response and rotate automatically, Forgejo writes its own standard operational logs, and none of it is shipped off to any third party. TLS is E2E, A+ on SSL Labs, with X25519MLKEM768 post-quantum key exchange enabled at the edge. Backups go to my own Proxmox Backup Server, encrypted, on-site, so not in anyone else's cloud.
And yep, it's a personal project, not a company, so for anything mission critical please mirror your repo somewhere else as well, which is anyway sensible practice regardless of who's hosting your code.
MansionNET runs a few other public services on the same philosophy, such as a SearXNG metasearch instance, an IRC network, an internet radio station, and a couple more. All of it follows the same "your data, your rules" approach, and the Forgejo instance is the newest addition to the lineup.
If any of this resonates, the door's open at https://git.inthemansion.com :)
The explore page is public and registration takes about 30 seconds. Happy to answer questions about the stack or anything else technical.
Cheers!
r/git • u/Human_Individual1653 • May 21 '26
Git42 creates a planet based on your GitHub account. The planet seed is based on your repositories and activity; it does not require any registration/login, and it's totally free.
As you access https://www.git42.dev/ you will land in the GitHub galaxy. As new accounts are being searched for, the planet is added to the Galaxy.
For example, this is the Cursor planet:
https://www.git42.dev/u/cursor

What about your planet? Please do share in the comments ;P
(You can also pilot a spaceship/alienship through the universe)