Alternatives
Products that do what Gitboard does
Where every pull request is stuck, on one board
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16OS
Hey HN, Over the last year, I’ve reviewed more than 1000 code changes. Most of the time was spent catching obvious mistakes rather than debating complex design decisions. If we estimate ~10 minutes per review, that’s 160+ hours spent reviewing code in just one year. So I thought: could I get some of that time back using LLMs? That's why I spent the last few weekends building Presubmit.ai, an open-source AI reviewer that runs as a Github Action right when you open a Pull Request. The results so far are promising: I estimate it can reduce the review time by 50%, which in my case would mean I…
2024 · github.com
- 17GC
We built a Git-native CLI tool that automates Git branch stacking. Here's why stacking matters and how GX helps: Code review is a notorious bottleneck. You write a large PR, wait for review, get feedback, iterate, and wait again - especially painful across timezones. Meanwhile, you're blocked from shipping dependent changes. Stacking lets you parallelise development and code review by breaking changes into logical and dependent chunks. Current stacking tools will consider each commit its own PR, but GX will automatically group commits into separate stacks while optimising for structural…
2025 · github.com
- 18AG
I built a GitHub app that checks for uncompleted checkboxes within pull request comments and blocks the merge if found. This allows you to treat checkboxes as to-do’s and: * Open pull requests with a to-do list template -> make sure all steps are completed before merging * Leave to-do reminders for yourself as you work on a pull request * Leave to-do reminders for someone else as part of your code review Especially useful for large PRs with collapsed comments.
2024 · github.com
- 19
- 20BA
2018 · github.com
- 21BC
Hey HN, I'm Fedor (solo founder). After ~20 years of watching devs fight Git, I'm building Branching. Branching streams your local edits to teammates in real time - no manual push/pull. It's Git-compatible and works offline. Why you might care - Teams see each other's changes instantly instead of in PR-sized batches - Conflicts surface ASAP while context is fresh (LLM-assisted merge is experimental, off by default) - Same GitHub remote, so no migration Ships today - VSCode extension + desktop app (macOS / Windows / Linux) - 3 small product teams have been using it for 1–6…
2025 · branching.app
- 22AQ
2014 · gitquiz.com
- 23AS
Hi HN, I built a simple tool that summarizes your team’s git logs into a weekly update that teams can send to leaders, other teams, etc. I hated writing the same update multiple times a week to everyone asking “what’s the status of X” Copy your repo’s commit logs with git log —all —since=“1 week ago”, paste them, and get a well-formatted update. Planning to add Github integration to further automate. Curious what folks think.
2024 · syncup.ai
- 24IC
Hey HN, I built ShadowGit a while back to automatically commit code every minute to a hidden git repo (.shadowgit.git). Original goal was to easily rollback when AI tools break things. But I discovered something interesting: this minute-by-minute history is perfect context for AI assistants. So I built an MCP server that lets Claude/Cursor query this history using native git commands. The results surprised me: Before: Claude would read my entire codebase repeatedly, burning 15,000+ tokens to debug issues. After: Claude runs `git log --grep="drag"` finds when drag-and-drop worked,…
2025 · shadowgit.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →