Alternatives
Products that do what layer does
Keep local repo files out of git without changing .gitignore
- 1HC
2017 · twistlock.com
- 2GM
2014 · presslabs.com
- 3

- 4

- 5

- 6

- 7

- 8AV
2012 · github.com
- 9GU
2013 · gitignore.io
- 10

- 11

- 12

- 13IB
If you ask why there was .hg and .hgignore in a Git repository, it's because I completely forgot this project is my first ever project using Mercurial as SCM. As such, I foolishly `git init` the repository and have to update both .gitignore and .hgignore to finish the changes. You can also see the Mercurial version of this thing at here: https://hg.sr.ht/~tsukii/robin
2022 · github.com
- 14GG
2021 · mapps.makeall.dev
- 15GF
2014 · github.com
- 16GX
Hi, I built a little service to fetch .gitignore file on terminal. I built this to avoid finding gitignore files while working without a github repo. I wanted to keep the size as small as possible ( 2.2kb ) and the UI simple. I would love to hear your feedback on this. https://gitignore.xyz P.S this is my first fully completed app in production. I would love to hear your feedback on this. edit: I'm running this on scaleway node in Paris, that's why the 100ms+ latency
2016
- 17RA
I built a CLI tool that lists out all the local git repos within a directory in an easy to read table format including relevant information such as last modified date and the status of branches in the repo, along with whether it is synced with remote or not. It also includes a bunch of flags to get exactly what you want in the format you want. I got this idea as I was trying organize the large amount of local git repos I had. I also found it particularly useful when traveling since I use a different device. In these cases, it is really helpful to know which local git repos I forgot to push…
2024 · github.com
- 18AG
2019 · github.com
- 19GM
2015 · github.com
- 20IC
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
- 21OC
Hi HN, I built a small tool called oci2git, which converts OCI container images into Git repositories. Each layer in the container image becomes a separate Git commit. I created it to make it easier to inspect and reason about container image contents. Instead of dealing with compressed tarballs or running docker diff, you can just browse the resulting Git repo, run git diff, use git blame, or even bisect layers. It's a new way to debug, audit, and understand how container layers evolve. It's written in Rust and currently supports images from local OCI layouts and remote registries (like…
2025 · github.com
- 22CC
My team uses Claude Code daily, and the sessions have become some of the most useful artifacts we produce. But they're trapped in ~/.claude/projects/ on whichever laptop they happened on. There's no good way to hand a colleague "the session where I untangled the migration" so they can claude --resume it and keep going from where I left off. Enter ccgs: Share Claude Code sessions through an orphan branch (@ccgs/) in your existing repo's remote - Session files carry the author's absolute paths. On pull, ccgs rewrites the working dir back to your path so resume actually…
Jun 2026 · github.com
- 23MG
2011 · gist.github.com
- 24CC
We're two engineers that got fed up with context switching. Why do we need to do a git push, open a browser tab, wait for some task to actually start, bite nails (or read HackerNews) for 10 minutes or more while dependencies are being installed for the 100th time and finally end up with an invalid YAML error. And for some reason this usually happens in the final stage of the pipeline leading up to the inevitable git commits "Fixed", "Fixed again", "Test", "Really fixed this time". We can do better. We set out to build Zippy. A CI/CD system that works from your terminal. No context…
Mar 2026 · zippy.sh
Ranked by how close each launch is in meaning, then by votes. Refine with a description →