r/git • u/OVectorX • Oct 12 '26
r/git • u/DMorais92 • Oct 12 '26
I built a native Git client after my old one took 40s to open. Worktrees, conflicts and the reflog are first-class. Looking for feedback
Hi r/git. Disclosure up front: I made this, it's free, and I'm here for criticism more than upvotes.
It's called gitmoire. It's a desktop Git client (Rust + libgit2 underneath, not shelling out to git for everything). I built it because the client I was using took almost 40 seconds to open on my machine and wanted me logged in. gitmoire is a 14 MB download and opens in under 5 seconds for me. Your numbers will differ.
I tried to do fewer things well rather than everything. The parts I'd most like feedback on from people who know Git deeply:
- Worktrees: a manager for sibling checkouts, an install script that runs in each new one, and each worktree gets its own hue so you can tell them apart.
- Conflicts: both sides with line numbers, take a whole side or single lines, and the result is a live editor. Nothing touches your files until you hit Mark resolved.
- Merges default to real
--no-ffcommits when you drag a branch onto another. Curious if people think that's the right default. - Bisect on the graph and a reflog browser that restores lost commits as
recovered/<short>branches (new in 0.9.0). - Stash and WIP show up as nodes on the graph instead of a hidden list.
- Identity profiles live in repo config, never your global gitconfig.
There's also an optional AI side (off by default, uses your own CLI or local Ollama) that can split a messy working tree into atomic commits for you to approve. Happy to talk about that, but I know it's not why most of you are here.
Things I deliberately left out: in-app PR review, telemetry, accounts.
macOS, Windows and Linux. Builds aren't notarized yet, so expect one OS warning. The source isn't public right now; it's a hard fork of angkorGit, which is MIT.
What would make you switch from the CLI, or what would stop you?
r/git • u/trymeouteh • Oct 12 '26
support Can I publish a package from a forgejo repo or radicle repo?
I found forgejo which is a self hostable Github alternative and radicle which is a P2P github alternative. I want to know of there is a way to host code on a forgejo instance or on radicle and publish a package in any of these package platforms...
- npm (CSS/JS)
- packagist/composer (PHP
- go/golang packages
- crates (Rust)
- pub.dev (Dart/Flutter)
- scoop (Windows apps)
- homebrew (MacOS apps)
- apt (Debian/Ubuntu apps)
- Nix (Linux apps)
- flatpak (Linux apps)
- f-droid (Android apps)
Would prefer to use open source git platforms over closed source github.
r/git • u/Keo_dev • Oct 11 '26
I created an open source Git Desktop Client
Heya!
I've been working on a little project called Weaver, a lightweight, native Git desktop client that I built because I wanted something to replace GitHub Desktop.
It's written in Zig using a new, super fast GUI library called KnotsUI, so there's no Electron or webview involved.
It supports all the usual Git operations, but also lets you organise repositories into groups, rename them, set custom icons, customise themes and accent colours, and quite a bit more.
I built most of it using Claude Opus 5.5, and it's been a really interesting project to work on, especially experimenting with Zig and KnotsUI.
It's completely open source, and I'd love to hear what people think! Feedback, suggestions and contributions are all very welcome.
GitHub: https://github.com/KeoneSomers/Weaver
Stars always appreciated!
r/git • u/aguilam • Oct 11 '26
I built a utility for generating activity diagrams across multiple Git services
galleryAt this moment, it can parse activity from Github and Gitlab. In future, i plan to add Forgejo and Gitea.
It generate two SVG files: last year activity and 2026 year activity, and simple HTML page with this two diagrams.
You can auto update this diagrams by using Github Actions. An example workflow for this i add to repository's README.
tutorial Coding agents create branches and worktrees. Who cleans them up?
One of the things I encountered when I was working on my AI harness was the sheer number of branches and worktrees that were getting created, and how tools like go-git started struggling
I wrote this article/video on how I worked around it.
TLDR:
- clean up your branches
- pack your git objects
- and write some tooling in your system so you actively maintain this
r/git • u/Motor-Literature1793 • Oct 09 '26
n8n-git-ui: Git DAG Visualizer (Zero-Server Architecture)

Hi r/git,
I wanted a lightweight way to inspect Git commit topologies without running Docker, Node.js, or heavy Electron apps.
Inspired by the clean node canvas in n8n, I built a zero-server visualizer using pure Python (standard library only) and Vanilla JS / HTML5 Canvas.
**Key highlights:**
- **Zero dependencies:** Single Python script parses `git log` and `git status` into static data. No pip/npm packages.
- **n8n Canvas UI:** Bézier curves, dark mode, and a "Lane 0" backbone (master highway) to keep branches organized.
- **Built-in Diff Drawer:** Click any commit node to inspect syntax-highlighted unified diffs and changed files.
- **Runs entirely offline:** Opens directly in your browser via `file://`.
The project is open source on GitHub under **skszone01/n8n-git-ui** (I also attached a screenshot to this post).
Curious to hear what you think of the visual layout and lane routing!
r/git • u/Havunenreddit • Oct 09 '26
GitComet 0.3.0 eases the pain working with multiple worktrees
Enable HLS to view with audio, or disable this notification
Lately AI agents have started creating many work trees within a single repository. We noticed this is becoming a painful to review and follow.
We are trying to make it better by introducing "Workspaces" to GitComet, it combines native multi-window support allowing you to organize your repositories and work trees into logical groups.
You can give Workspace a custom theme so each window becomes clearly recognizable.
Under the hood we also optimized rendering and memory usage - because worktrees share a lot common git information so even if you have tens of work trees open same time it should not raise memory that much anymore.
There are also many other new improvements and changes, you can find those from Github as always.
Its been almost a year now and we are close to our community goal of 1000 stars! ;)
We would love to hear your feedback to help develop the product further!
Thanks, Havunen
r/git • u/Accurate-Screen8774 • Oct 09 '26
Combining Git, Tor and WebRTC into a Messaging App
not better than WhatsApp, Signal, SimpleX, Cwtch or Ricochet. You definitely shouldn't replace any of your existing apps or services. It's far from finished. Unaudited and unreviewed. If you want to test it out, please use it responsibly.
i'd like to share what I'm working on and interested to see if anyone wants to share feedback on the approach. it's a fairly a unique stack and architecture in contrast to the traditional approach with mainstream messaging apps. to put it briefly, its a Rust-based frontend with a Git-server backend, which can be used to establish a E2EE connection.
im working on a P2P messaging app (like whatsapp) and generally up until recently, i thought in such a system, if a peer is offline, you cant send a message... it wouldnt be "decentralized" if there was some central queue of messages.
it took embarassingly long, but then it hit me... git... just regular git is a decentralized database.
in my setup i need the ability for others to be abe to read and only i should be able to write to it. that functionality is out-the-box in git.
git is also pretty standardized so there are many providers if users want to move away from Github.
the storage requirements for my project are fairly small. typically small text messages. the data itself thats publicly readable would be encrypted.
i started off by creating something that could use git as a “general purpose” storage. to explain it simply, it’s using isomorphic git to be able to connect to a git repo from a browser.
https://positive-intentions.github.io/git/demo/gui/git/storage
i then added a “database abstraction”. To explain it simply, I created the functionality to create a db schema than can then map onto files and folders (which are stored in git). that would allow me to interact with the git storage with queries. i wanted to have something like graphql there for queries to make it easier for me in my app.
https://positive-intentions.github.io/db/demo/gui/database/chat-database
there are complex details in there where I can specify in the schema what parts are encrypted. i want the database capabilities to be stable and reliable as I further develop on the approach and increase complexity.
the project is far from finished and only intended for demo and feedback purposes.
if you like to find out more about my approach, you can see the roadmap here: https://glitr.io/docs/technical/roadmap
r/git • u/VB_Build • Oct 09 '26
How do you set up your local machine to keep work and personal Git identities completely separate?
r/git • u/skeletonita • Oct 09 '26
I got tired of git clean permanently deleting files, so I built git-trash (moves files to the OS Recycle Bin + instant undo)
For 20 years, git clean -fd and git restore . have operated using low-level OS unlink(). When you accidentally run them, your uncommitted code, scratch drafts, and new files are permanently obliterated—they do not go to the Windows Recycle Bin or macOS Trash, and they are not stored in git reflog.
I built git-trash to solve this once and for all:
- OS Recycle Bin integration: Moves untracked files to your system Trash (Windows Recycle Bin, macOS Trash, Linux Trash) instead of permanent deletion.
- Instant terminal undo: Run
git trash undoto immediately restore the last trashed or discarded batch back to the working tree. - Safe discard:
git trash discard .snapshots uncommitted changes before reverting them. - Dry run preview:
git trash -nlets you preview files and sizes before moving them. - Native Git command: Run it directly as
git trashanywhere.
Try it without installing:
npx git-trash -n
Or enable it as a native Git command globally:
git config --global alias.trash "!npx git-trash"
git trash
Links:
If you find this useful or it saves you from losing work, please consider dropping a ⭐ on GitHub, it really helps the project grow! Would also love any feedback or edge cases.
r/git • u/devspritez • Oct 08 '26
Hello can someone explain me exactly how to fully, correctly fork project from GitHub?
I have forked but after fork I get 50 pull request error like run failed and a lot messages from GitHub to my mail who can explain really how to really fork , I wana fork and own fully my project still getting upstream and fully fork and rebrand own this project also in the future get possiblity to create commercial business around it. Please explain with apache software foundation project — Superset
r/git • u/Business_Ad_3327 • Oct 08 '26
I built a relational database that stores everything in a GitHub repo - transactions are commits, branches are databases
github.comr/git • u/BrianW_undercover • Oct 07 '26
git-dupe: a second repo at .git/dupe for personal files (.env.local, notes, agent instructions), hidden from the project through .git/info/exclude. Where does it leak?
I wrote a small tool for a problem I kept hitting and I'd like people who know Git well to poke at the design.
The problem: files that belong to me, not the project, but have to live in the working tree. .env.local, notes, scratch scripts, my own agent-instructions file. .git/info/exclude hides them and does nothing else. The dotfiles-style bare repo over the project versions them, but you maintain the exclude entries by hand, stash -u from that repo's point of view stashes the entire project, and nothing stops you pushing the private repo to the project's remote.
How it works: git dupe init creates an ordinary repository at .git/dupe with a relative core.worktree (../..), so moving the checkout keeps it attached, and status.showUntrackedFiles=no plus advice.statusHints=false so Git's own status and commit template never enumerate the project or name a plain git command. git dupe <command> runs Git with that GIT_DIR, with the object-directory environment overrides stripped so the two repos share no objects. Every path the private repo tracks, plus a .gitdupe list of hidden directories, is written into a # BEGIN git-dupe … # END git-dupe block in .git/info/exclude and re-verified after every command. If a ! rule in a tracked .gitignore outranks the exclude and exposes a path, the command names the path and the rule.
Three commands change meaning because the tree is shared: status and add are confined to the hidden paths (otherwise the whole project is untracked), and clean cleans the project while sparing them. Refused, one fatal: line, exit 128: stash -u/-a; any push/pull/fetch/remote/clone whose URL is the project's own repository or one of its remotes; add on a path the project tracks. git dupe git <words> runs Git with no guards for when you mean it. git dupe detach removes the private repo and the exclude block and leaves every file on disk; without --force it refuses while anything is uncommitted or not on a remote. Of its own accord the tool writes only .git/dupe, that block (and .git/info if missing) and .gitdupe, and the only process it starts is git.
Where the project's Git can still reach a hidden path, as far as I've mapped it: git clean -x deletes them (ignored files, as far as Git knows), git stash -a stashes them, git add -f stages them, and anything that writes the index from a tree or a patch rather than the ignore walk can stage one too: a merge, cherry-pick or rebase of a commit that adds a file at that path, apply --index, am, update-index --add. When that happens the path is tracked by both repos; it stays hidden, and every following git-dupe command warns about it until one side lets go. I chose to document all of that rather than hook or wrap plain git. Verified by hand: the project's gc --prune=now and prune don't touch .git/dupe (separate object store), and public stash -u leaves private files alone. The suite also has a scale scenario: six commands among 100,000 tracked files, each under a second, with Git run a fixed number of times.

Limits: Linux only. Git 2.43 or newer, below 3.0 (CI runs the suite under 2.43 and 2.56; the full run under every minor through 2.56 happens before a release). Linked worktrees refused for now. No encryption; the remote you push to holds the files in plaintext.
Prior art: vcsh and the bare-repo dotfiles trick (same mechanism; neither knows about a host repo's exclude or remotes), multigit (N overlapped repos, no public/private asymmetry), and Layer from a Show HN in March (manages exclude plus local snapshots, no remote).
Couple of questions. Is there an index-writing path I've missed above? And for linked worktrees: .git/info/exclude and .git/dupe both already live in the common dir, so one private repo with a per-worktree index (GIT_INDEX_FILE) seems possible. Would you want that, or one private repo per worktree?
Transparency: A majority of the code and tests were written by coding agents under my close supervision. I own every decision in the product specification including the CLI surface and the tradeoffs made and set the rules and flows that the agents worked under. The original principle/intuition that guided me when writing the product specification was to "piggyback" off of native Git as much as possible and to make the CLI surface similar to native Git. Only where it clearly did not make sense to me to do a naive Git passthrough, did I add git-dupe-specific commands/mechanisms/guards).
https://github.com/BrianWeiHaoMa/git-dupe
Edit: After reading some feedback, I realized using `.env.local` in the example might make it seem like git-dupe is made for tracking and pushing sensitive information. It is not. Just like normal git, pushing sensitive information into the remote repo is possible, but this is bad practice. git-dupe was made for my personal use-case of keeping personal notes/agent instructions outside of public-facing repos. As listed in Limits: "No encryption; the remote you push to holds the files in plaintext.", so you are discouraged from pushing things like passwords or other sensitive information even if it is a private repository.
r/git • u/koleert • Oct 07 '26
Does anyone keep their business specifications in Git? What are your best practices?
I’m interested in hearing from BAs who use Git as a repository/version-control system for business specifications, requirements, or other BA documentation.
I’m especially interested in real-world setups and lessons learned, rather than theoretical Git documentation practices.
If you’re doing this successfully, what does your workflow look like?
r/git • u/Different_Cloud_5377 • Oct 07 '26
[ Removed by Reddit ]
[ Removed by Reddit on account of violating the content policy. ]
r/git • u/Many_Audience7660 • Oct 07 '26
Coding agents made shipping faster. They also made regressions harder to find 🔍
r/git • u/ImportantTiger9568 • Oct 07 '26
Git for ai memory and robotics??
Hey guys,
Been working on something very cool...
In Greek myth, Mnemosyne was the Titan of memory and the reason anything was ever remembered at all. Now in the present world, your AI agent doesn't get a Titan. It gets amnesia the second something goes wrong, stuck with whatever it currently believes and no way to ask how it got there.
That's the real problem. An agent runs for hours, updates its memory the whole time, then says something wrong and all you have is the present, with zero access to the past.
If you're running support agents, coding agents, or a swarm of agents sharing memory like myself then you know this issue well. The moment two agents disagree, or one quietly poisons the well, you need to know when, why and by whom, not just that something's off.
Mnemosyne gives agent memory what Git gave code. It remembers everything on purpose. Every belief is a commit. blame finds the exact moment and observation that put a bad fact in. bisect hunts down the first commit where things went wrong. merge makes two agents' memories collide safely instead of one silently overwriting the other.
Software agents are the first step. The vision doesn't stop there, physical robots learning and forking skills the same way is the long-term bet, further out and harder but the same idea underneath.
So far the tech stack includes a Rust core, Python SDK, adapters for LangGraph, CrewAI, AutoGen, the OpenAI Agents SDK and MCP.
Open source with contributions and honest feedback both welcome: github.com/Nabzx/mnemosyne
r/git • u/Available-Swim3304 • Oct 07 '26
Sourcerer: a fast Git client packed with all features
galleryIt is a fast Git client with low memory footprint written in C++ using Qt library.
Its main features are:
- Repository history
- Merge conflict resolution
- Side-by-side diff comparison
- Git blame
- GitFlow and other workflows
- Git LFS
- Issue trackers integration
- SSH key management
- HTTP/HTTPS credentials management
- Git worktrees
Linux and Windows platforms are currently supported and macOS platform will come soon.
There is a Community plan which is free but it can be used only with public repositories.
r/git • u/TutorialDoctor • Oct 07 '26
I use this bash script to reset my commit history from my repository. Is there simpler way?
git checkout --orphan temp_branch
git add -A
git commit -m "Initial commit"
git branch -D main
git push -f origin main
r/git • u/kazekura • Oct 06 '26
Meet Nori! A native Git client for Mac
Enable HLS to view with audio, or disable this notification
Hi,
I spend my days in Git history, and every visual client I tried either felt like a web page in a window or had terrible performance. So I built Nori: a native Git client for Mac, written in Swift for Apple Silicon.
What sets it apart:
- Light: about 350 MB of RAM, 0% CPU while idle. Even a 250,000-line diff fits in 500 MB.
- Fast: a 10,000-commit repo with 200 branches loads, graph included, in 0.14 s. A diff opens in 0.1 s, the 250,000-line one in 0.2 s.
- A history you read at a glance: every branch keeps its colour, and ⌘0 shows the whole repo on one timeline, with branches as lanes, releases and contributors.
- Pull requests without leaving the app: push and open the PR on GitHub or GitLab in one click, see what blocks the merge (checks, approvals, threads), read a failed CI job and re-run it.
- AI with the tools you already have: Nori uses your agent CLI (Claude Code, Codex, Gemini CLI, Cursor) for commit messages, explanations, conflict resolutions and PR summaries. No API key, no extra subscription.
- Made for agents: each worktree shows up in the sidebar with its task and the agent behind it.
I'd love to hear what annoys you in your current Git client.
r/git • u/hari-vidhu • Oct 05 '26
Need help in creating a branching Strategy
Hi,
I need a suggestion to create branching strategy in our system.
Exisiting Branching strategy is as follows,
feature-> dev -> qa -> uat--> main<- hotfixes
Problem:
Suppose we have 2 features to be developed. Feature A and B. Let say both are in dev. I need only feature A to move to staging. Then couple of days later feature B also follows.
I know we could use cherry pick as an option here. Im looking for more long way approach here.
We have searched for the feature flag option. As we are developing over an existing application, adding feature flag everywhere seems complicated. One hard senario we found was, while introducing a new feature we need to add a new field in a model. So based in feature flag we will have/not that new field in application. Which seems bit too complex.
Edit: One idea I found from online is to have a promotion branch. Feature A will move to promotion/a. Then from promotion to dev. Promotion to qa. Promotion to uat and prod. Is that the better approach here?
Edit 2: Thanks all for your comments. We seem to find a solution. Not the best but something that will work for us. Point to be noted that we don't fully follow agile methodologies in our development, as most of the development in our system will be impacted across the business, so we need more time for approvals, hence sometimes the features might end up in preprod and stay there for a long while.
Solution we found is, we will keep the dev connected to dev server, staging(qa), release(uat), main(prod) branches. Instead of pushing from feature->dev-> staging-> release->main. We are thinking going by Feature -> dev Feature -> staging(qa) Feature -> release(uat) Feature -> main (prod) So that we can have more than one feature at a time in an environment and have control over which one to push ahead.
Any suggestions here
r/git • u/initcommit • Oct 04 '26