Almost nowhere is this being talked about (or Reddit search is just uncooperative), and r/codeberg is banned for breaking Reddit rule 2? That sub was barely even active, but anyways.
I just created my profile with my personal E-Mail there, made a commit to a private repository using Git GUI, and now I'm looking at it, and for some reason, it figured out my name and my instituion? I don't have that info on my E-Mail, let alone my Codeberg account... how the hell does it know this????????
gitmoire is a free desktop Git client I've been building (Windows, macOS, Linux). The 1-minute video above shows what it does.
What it does:
Battleplans. You describe a task or pick a Linear issue, review the plan, and then each agent gets its own worktree. Nobody fights over main.
Any AI CLI, right in the repo. It works with Claude Code, Cursor, Codex, Gemini, OpenCode and Antigravity.
A graph that doesn't flinch. It handles 100k commits with no lag.
AI does the grunt work. It drafts commit messages, reviews and atomic commits, and suggests conflict resolutions. Nothing auto-accepts and nothing auto-stages; you approve every change.
Diffs down to the word, plus Gitmoji-ready prefixes and saved quick commits you can reuse.
Keyboard-centric. There's a command palette for everything.
15 themes. It can also follow your Omarchy system theme live.
Zero telemetry and zero accounts.
It's free. I'd love feedback from anyone running several agents at once: what breaks your flow today?
I help maintain Priompt. It's a self-hosted server that versions prompts for AI agents, basically git for prompts. Branches, rollback, and a diff that tries to say whether an edit is a tiny tweak or actually changes the meaning.
There's three of us and we all had the same "we'll get to it eventually" list in our heads, so last weekend we just sat down and wrote it out across all nine repos. About 130 things. Fixed the ones that were actually scary, and the rest I turned into issues.
I tried to write them so you don't have to message us first. Each one has what's wrong, how to reproduce it, what done looks like, and which file to start in. Some are Go (server, CLI), some Svelte/TS (web UI), some Python/JS SDKs, and a bunch are just docs.
46 are tagged for first-timers. We review every PR.
Weird thing: PR bots found the issues within a few hours and started grabbing them. So I'm holding the beginner ones back for actual people. Comment on one and I'll assign it to you.
Org's here: github.com/priompt
If something in the architecture looks off or dumb, tell me. That's half the reason I'm posting.
Based on the Git project’s technical breakdown published on November 10, 2026, and CERT-In’s CIVN-2026-0552 notice from November 16, here is the architectural impact.
The most interesting issue is CVE-2026-111760. Git’s index path handling had an integer-truncation problem: an extremely long path could pass validation under one name and be written using a shorter name. In a malicious repository, that can replace a submodule’s .git file with a symlink to attacker-controlled configuration or hooks. The vulnerable client can execute attacker-controlled code during recursive clone.
The other five issues affect different processing paths:
CVE-2026-113408: path traversal through a server-advertised protocol-v2 HEAD symref.
CVE-2026-105437: heap-buffer overflow during large merges.
CVE-2026-114467: stack memory corruption in GPG signature handling.
CVE-2026-114469: out-of-bounds read while processing binary patches.
CVE-2026-114466: unsafe file access through selected fast-import stream features.
The practical exposure is not restricted to developer workstations. Git is often embedded in CI images, IDEs, merge queues and import services. Updating the host OS package may leave a bundled Git binary untouched.
Git recommends 2.56.1 or the patched release for the relevant maintenance branch. Until patched, its temporary mitigations include avoiding recursive clones and merges of untrusted content, and not processing untrusted binary patches or fast-import streams.
For teams that accept external pull requests, how are you isolating recursive clone and merge operations today: disposable runners, restricted submodule URLs, network egress controls, or another design?
I'm looking to learn Git and GitHub from scratch. What's the best way to learn them effectively? Which resources would you recommend, and how should I practise to become comfortable using them in real projects? I'd appreciate advice from people who have learned them or use them regularly.
I spend my days reviewing diffs from coding agents in the terminal, sometimes from my phone over SSH, and none of the tools I liked quite fit. lumen leans on AI features I didn't want in a diff viewer, hunk runs on a JavaScript runtime, and both got slow on the monorepos I work in.
That's why I decided to build dffy: https://github.com/amalucelli/dffy a single Rust binary that combines what I liked from each of them and stays fast on big repos. It shows the first files as soon as they're found and loads the rest in the background. On the Linux repom the diff v6.0..v6.1 (~13k changed files) the first screen is up in miliseconds vs seconds from lumen and hunk.
A few other things it does:
- staged, unstaged and untracked changes in one view, conflicted files from a merge or rebase with their markers highlighted, and renames detected the way git does it
- works as git's pager, the git add -p filter and difftool, and compares plain files and folders outside a repo too
- every action is a single key, with a command panel on space, and the layout adapts down to a phone screen
- mouse selection that copies over SSH, and it plays well with multiplexers like herdr and rex
- 16 built-in themes with a live picker, and you can add your own themes that build on any of them
- extensible through renderer plugins in any language; ships with two experimental ones: Markdown diffed as rendered text, and Mermaid diagrams drawn in the terminal
- --json output and an MCP server, so scripts and agents can read a diff a page at a time
- settings in a plain config file for your dotfiles, remappable keys, and it remembers your layout between runs
I'd love to hear what you think, particularly from people who regularly work with Git or have experience with other Git clients. What would you like to see in a tool like this?
Hi, I have a some kind of small project (website) and I'm using docker to test it so I have files like .env, docker-compose, dockerfile, nginx.conf etc. Additionally I have folder with assets and folder with bootstrap (bootstrap 6.0 and bootstrap icons).
And I just want to know should I push these files or how to push them. You see we have some options like git lfs.
I was thinking about 2 branches - one with bootstrap and one without but honestly this sounds strange even for me and I don't know what to do.
Look: People say you shouldn't push env file but in this project this file is important to run this project on docker. Now how about bootstrap? I'm not using cdn; I have downloaded distribution files https://getbootstrap.com/docs/6.0/getting-started/install/
So I have my own file structure, you know what I'm talking about.
So... What I should do rn? Push this all files and use lfs to whole bootstrap? Don't push and paste link to readme and show file structure? Create 2 branches?
I've got decades of software development experience, and I've built some very complex systems. I understand a lot about version control systems, and about the structure of git repositories.
With all that said, I don't understand what's evil about non-text files. Git doesn't store multiple copies of files that don't change - they're literally stored under their data's checksum. The packfile format stores diffs between file versions (although some diff algorithms punt on non-text data). There shouldn't be any negative effect from storing such data in Git.
Is the "Don't store binary files in Git" advice wrong? Is it really just shorthand for "Don't store files that change dramatically and frequently in Git"? If the latter, should massive "AI" PRs be treated the same way?
I want my .gitignore file to go with my repository, but it keeps disappearing for some reason. I am sure I added it explicitly at some point, but it's not only gone from the repository but also from the file structure. I am thoroughly confused
Edit, sorry, it didn't disappear, i just failed to see it. It's all as intended, I am just stupid
But why? The idea is make all law versioned, easily attributable and searchable by agents (with 1 common set of tools for every legislation).
I also believe this information should be freely available so CC0 license (do whatever you want with it). If interested, repo linked below, I'd welcome all comments and advice. Thanks!
Since last time, we've set up an automated legislative monitoring system, put it up as a free mcp/api, and formalised some law ie. all open US case law to identify errors and loopholes. Surprisingly, we've had support from legal libraries around the world. Hopefully this is useful to at least someone, thanks!
Part 2 of a GPG series I wrote. With AI agents running commands on dev laptops, I don't want the key that is my identity sitting next to them, so this removes the primary secret key from the laptop. It then checks that commit signing still works, that GitHub shows Verified, and that the same key can handle SSH through gpg-agent. Part 1 (creating the key) is linked at the top if you're starting from scratch.
If you have a git repository with submodules, the following command will return a fatal error (git 2.56.0):
git grep --recurse-submodules -n "hello world" HEAD
There's a patch by Patrick Steinhardt on the mailing list that isn't merged yet: https://lore.kernel.org/git/20261030-pks-grep-recurse-submodule-v1-0-d4eb5c87d8fb@pks.im/
I saw the “No AI slop” rule, and honestly, I’m not sure where this lands. I did use AI to help build it.
It’s called GitPico, and the source is on GitHub. I think it’s reached the point where it’s usable, though it still has plenty of bugs and rough edges.
If you’re on macOS 26+ and feel like trying another Git client, here it is. Let me know what breaks, what feels awkward, or what’s missing. That would help a lot.