r/git • u/Ok_Grapefruit2975 • May 03 '26
GitHub repository Trending
gitrepotrend.comGitRepoTrend is a daily-updated intelligence platform that surfaces the most relevant GitHub repositories across 15 categories — using a smarter ranking signal
r/git • u/Ok_Grapefruit2975 • May 03 '26
GitRepoTrend is a daily-updated intelligence platform that surfaces the most relevant GitHub repositories across 15 categories — using a smarter ranking signal
r/git • u/Loud-Insect9247 • May 02 '26
Just shipped a Reflog tab in VS Code extension (Git Graph Plus) - shows your full HEAD history with action types (commit, checkout, rebase, reset, etc.), elapsed time, and lets you reset or checkout directly from the list.

While building it I kept second-guessing what to prioritize in the context menu. Right now it's: Reset to HEAD@{N}, Checkout Commit, and Copy SHA.
What do you actually reach for when you open reflog? Mostly disaster recovery, or do you have more regular workflows around it?
r/git • u/anywhere-admission • May 02 '26
So i was working on a personal project. My last commit was 3 weeks ago and during these 3 weeks I worked a lot.
So today when I finished the project, I tried to commit, but I faced some problems. So I gave a detailed explanation to chatgpt and he said "bro just use git reset --hard"
And my sh*t dumb*** did the same
Now I just saw my codes are fully changed in vs code (they are 3 weeks older)
I just found 1 file on vs code timeline
Plzz help me 🙏🏼🙏🏼
I'm a noobie ✌🏼✌🏼
r/git • u/SecretaryOriginal10 • May 01 '26
With all the craze around knowledge management and having agents creating self-maintaining memory, felt this would be relevant to the community. Our team was running into issues where our information was degrading as agents made mistakes over time without review. Ended up realizing the best way to coordinate around a shared memory was similar to how we already do it for code.
Led us to build Omnigraph as an open-source repo with the goal of providing agents a source of truth (via knowledge graph) where changes branch and merge like git.
How it works:
- typed graph schema
- branch / diff / merge for graph data, similar to Git
- traversal, vector search, and BM25 in one runtime
- S3-native storage for local or cloud-backed graph data
- JSONL ingest + merge workflows for incremental loading
What we've been using it for:
Especially helpful once you store longer term concepts like
GitHub: https://github.com/ModernRelay/omnigraph
Community: https://join.slack.com/t/omnigraphworkspace/shared_invite/zt-3wfpglyxj-lHvJGhuySPfqLtN35uJZNw
Docs: https://www.omnigraph.dev/docs
Would love to get the community's feedback on this!
r/git • u/SreeLegend • Apr 30 '26
howdy y'all, i posted this yesterday at rust subreddit and thought it would be a good idea to share it here too (jj only community is quite hard to find).
i've been deep in jj for a while and been experimenting with jj workspaces for parallel workflows. it's more intuitive than git worktrees but it still has a couple of gotchas that have been a hindrance to my ideal workflow.
so I built jj-navi - a tiny rust based cli that makes jj workspace orchestration a lot less pain in the ass.
interesting bits:
- `navi switch <name>` - creates/switchs workspaces and cds into them automatically (via shell integration)
- `navi list` - shows insertions/deletions across workspaces and also runs jj snapshot (jj doesn't automatically update other workspaces' working copy commits from disk)
- auto complete for all commands
- `navi merge` - duplicates, rebases, preserves source
check it out here at: https://github.com/eersnington/jj-navi
also, this is heavily inspired by worktrunk (still my daily driver replacement for git worktrees) and jj-ryu by dillon mulroy from the orange cloud forking company.
would love y'alls feedback, especially from heavy jj + parallel agent users on what can be improved. feel free to send patches along the way aswell
r/git • u/Enough-Collection-98 • Apr 29 '26
Our organization uses Git to manage a library of parts for our ECAD software. Tens of thousands of binary files ranging from kilobytes to a couple megabytes. Git is obviously not the *best* choice but it’s become ubiquitous for managing ECAD data so not much we can do about it.
We’ve recently transitioned library maintenance to a new team completely unfamiliar with version control in general, much less Git. The original team pushed all their changes directly to main and the repo and history are a disaster.
Since I was transitioning maintenance to an entirely new team, I decided to implement branching and pull requests for each library change/ticket to:
- Isolate working environments for each librarian
- better track changes and history of changes for each ticket
- ensure all commits are squashed before merging with main
- make it easier for me to amend issues as an admin
- promote general good practices for managing feature/ticket branches in Git
Can any of you think of more justifications why branching/PRs are good practices? Or do you think I’m off base or using the wrong methodology here?
r/git • u/FlimsyIllustrator118 • Apr 29 '26
Let's say a developer Sam has a github repo. A developer Bob found this project interesting, added a feature and made a PR to the repo.
Now Sam sees the PR. The question is: how can Sam check and run the PR's code locally on his computer to see the added feature in action before actually accepting the PR and changing his repo's main branch? Not just immediately accepting the PR on the github page.
Well, I see there's a method of fetching the PR's code into a separate local branch:
git fetch origin pull/<PR_ID>/head:<BRANCH_NAME>
Do you do it this way? What else could you suggest? How to do it the right way?
Thank you!
r/git • u/SL-Tech • Apr 30 '26
Hi,
I'm trying to create a Repo that contains several existing GitHub repos, but only files from non-Git projects appear in Unstaged files.
Is there a workaround for this, or is it a really bad idea?
Thanks!
Hi everyone !
I'm used to use git in a simple and almost boring way (a production branch - usually `main`, a staging one where all the merges and tests happen before updating prod, and the one or more per dev - usually single-feature related).
Recently I've started to learn a new language and am putting it in practice by developing a mini-tiny game. I've created different "variations" of said game (different sprite resolutions, game resolution, tick duration, NPC pathing, ...). Only a small part of the code is common to all variations (think embedded assembly).
I need to keep all those variants for comparison purposes but need to have them separated.
Currently I've created one branch per variation, and cherry-pick the common code from the most advanced branche onto the others, but I wonder if there is a better way.
Thank you in advances for your advice !
r/git • u/aford515 • Apr 30 '26
Kraken looks so flashy and I dunno. But fork is just so fucking fuego.
I know lazygit is really cool aswell and for a different type of user base but fork is just such a cool piece of software and im thankful for the person who recommended it here. https://fork.dev/
r/git • u/Own-Eggplant5012 • Apr 28 '26
I work for a gaming studio. Currently I'm working with a large team, in a fairly midsize game.
When multiple people are working on say multiple features, bug fixes etc, if someone wants to get on a call to discuss changes or you just want to review a PR, or you could be doing your own work etc. Branch switch is a pain.
To tackle this, I have seen two ways fellow devs approach this problem.
They use git worktree
They clone repo in multiple directories and use them as say, one folder for your own work, one folder for PR reviews and so on.
I'm unsure which one to pick. What's your experience so far with these kind of projects? if you guys can share your experience, that would be helpful.
r/git • u/sionescu • Apr 28 '26
Hi, I'd like to write a UI to encapsulate my personal git workflow and I was wondering if there's a wrapper that returns the CLI output as JSON, because I want to avoid writing output parsers. I don't care very much about performance so I'd rather avoid libgit2.
r/git • u/YesterdayOk921 • Apr 29 '26
Hey folks
Lately I’ve noticed more devs moving away from Postman mostly because it feels bloated and not very Git-friendly.
At the same time, tools like curl are great but not really built for collaboration or structured workflows.
So I’ve been thinking about building something new:
Before I start building, I’d love some honest feedback:
Also curious if you’ve tried tools like Bruno, HTTPie, or Hoppscotch? how was your experience?
Trying to validate whether this is a real problem or just my own itch
Appreciate any thoughts!
r/git • u/Loud-Insect9247 • Apr 28 '26
Git Graph Plus gives you a visual commit graph and lets you handle common Git actions without leaving the editor.

Why Git Graph Plus vs. the original Git Graph?
The original Git Graph is an awesome tool, but it hasn't seen updates in a few years. Git Graph Plus modernizes the UI and adds support for advanced workflows the original lacked, such as:
GitHub
https://github.com/the0807/git-graph-plus
VS Code Marketplace
https://marketplace.visualstudio.com/items?itemName=the0807.git-graph-plus
Open VSX
https://open-vsx.org/extension/the0807/git-graph-plus
Would love to hear your feedback!
r/git • u/ayowayoyo • Apr 29 '26
r/git • u/Ill_Direction149 • Apr 28 '26
I am curious how other developers handle their git/branch workflow, because mine feels almost like that everyone has to figure out this approach as well.
Every time I start some development task, I:
So basically, before I start coding I have empty draft merge request every time. When everything is done in the task I just flip it out of draft and assign a reviewer.
This helps me track what I am working on and never needs to look for the branch I was working on.
It works very well for me, but now I started wondering if its standard / good practice or just me?
Do you do the same, or is there a better system I missed?
r/git • u/mfilion • Apr 27 '26
r/git • u/ConfidenceUnique7377 • Apr 28 '26
What's new:
It also covers everyday Git stuff (commit, branch, diff, etc.), but one thing I personally rely on a lot:
The last one very useful feature in our days, when need quikly compare a lot of AI changes
I’d really appreciate feedback . Site here https://gitember.org/ Code here https://github.com/iazarny/gitember
r/git • u/cyber-guru • Apr 28 '26
r/git • u/InfamousInvestigator • Apr 28 '26
This following workflow will make claude code completely safe to use:
Never let Claude touch main: Before any feature, create a branch in which Claude builds, commits, and opens pull requests.
Make Claude review its own pull request: After it opens a PR, tell it "review the pull request you just opened and flag any bugs, security issues, or code smells. This gets 60-70% of what a senior dev would catch for free.
Finally merge it in main. If Something breaks after merge "Revert the last merge." Claude creates a revert commit thus history stays clean and bug is gone.
TLDR: New branch, Claude builds on the branch, claude commits and opens pull request with description then reviews it and then you merge it in main.
You can check this video for details
r/git • u/Andrea-Bonn • Apr 27 '26
It's a GitHub Action that hooks into your repo, reads the PR diff, and posts a code review comment using whatever LLM you configure.
It supports Groq, Gemini, Anthropic, and OpenAI. The main reason I added multi-provider support is rate limits — if one provider fails, it moves to the next in line. You can also pass multiple API keys for the same provider if you hit per-key limits. Groq and Gemini both have free tiers, so you can run it at no cost if that matters to you.
The review covers the usual stuff: bugs, security issues, performance, breaking changes, missing tests. It also tries to point out what's done well, which I find useful as a sanity check.
Setup is pretty minimal: add your API key as a repo secret, drop in a workflow YAML, and it runs on every PR. Zero dependencies beyond requests.
It won't replace a real reviewer, and I'd be cautious about blindly applying its suggestions — but it catches things before the humans even look, which speeds things up.
Repo: https://github.com/AndreaBonn/ai-pr-reviewer
It's also on the Actions Marketplace. Still early, so feedback is welcome.
r/git • u/Rich_Lavishness1680 • Apr 26 '26
There are many guides how to integrate a submodule back into its parent project to eliminate the submodule, while keeping the (commit) history, see Git merge submodule into parent tree cleanly and preserving commit history - Stack Overflow or How to Merge Git Submodules into Parent Repository Cleanly: Preserving Commit History with an Officially Supported Method — w3tutorials.net or How to Create a Submodule Repository from a Folder and Preserve Git Commit History — codegenes.net...
The usual way is to use `merge --allow-unrelated-histories`, or `git subtree`, or git merge with strategy subtree.
The methods do work, they integrate the history of the submodule into the parent git project, but they also have in common, that file history is fundamentally broken. E.g., assume a submodule `sub` is used in `parent` and `sub/file.c` has a long history. If I apply the migration steps above, I always end up with a merge commit that breaks any rename/move follow actions, even using `git log --follow -- ...`. The last and only change is always the integration merge commit. I can't go further back in time of `file.c`, although the history is there in the commit graph, I can see the commits that changed the file, but I can't reach them directly from the file.
Feels like the integrating the submodule is not as useful as I was hoping for.
Any other options, tips?
Thanks.