Alternatives
Products that do what Worktale Your Dev Story Told Beautifully does
Turn your git history into a record of what you built.
- 1
- 2
- 3
- 4GW
I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this. It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options. If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!
2025 · github.com
- 5
- 6GH
2021 · simonwillison.net
- 7
- 8IM
I'm excited to finally launch Outstatic, an open source static website CMS that doesn't require a complicated setup or signing up to a third-party service! You can access the documentation here: Outstatic Documentation. I invite you to start by deploying our example blog to Vercel and giving it a try. I think you'll be pleasantly surprised at how easy and fun it is to use Outstatic. Please, let me know what you think. This is the first public version of the project and all feedback is welcome. If you dig the project feel free to leave a star on Github. I appreciate your support!
2022 · outstatic.com
- 9
- 10
- 11
- 12IC
Personally, I think the JJ VCS (https://github.com/jj-vcs/jj) hit a point some time in this past year where I find it hard to find a great reason to continue using git. Over the years I've cobbled together aliases and bash functions to try to improve my git workflow, but after using jj, which works with ~any git repo and integrates great with Github repos, all of the workflow issues I ran into with git are not only solved, but improved in ways I couldn't manage with simple scripts. One example is the op log, which lets you go to any point in your repo's time and provides…
Oct 2025
- 13AD
2023 · gist.github.com
- 14
- 15GT
2017 · gitorials.com
- 16GT
Jun 2026 · gitstock.org
- 17GHGit Hooting▲124
00's called, they want their RSS feeds back. I was looking at my growing Github gist collection when a sudden urge to blog and make a name for myself "by not programming" struck. Part way into implementing my oh so special static website generator it occurred to me that, quite frankly, Github gists is a pretty decent publishing platform. I mean, it gives you reasonably extended markdown with previews, heck I could even write in org-mode, has comments, follower - followee relationship, extended search with filters, check out locally and push your edits. Did someone say "edit button"? Thus the…
2023 · git.ht
- 18
- 19GW
I context-switch a lot. Someone pings me about a bug while I'm mid-feature, and I either: 1. `git stash` (and forget what's in there forever) 2. Make a "WIP: stuff" commit (clutters history) 3. Ignore them until I'm done (not great) Worktrees solve this perfectly – each task gets its own directory, fully isolated. But the commands are clunky and I kept forgetting the syntax. So I built a small CLI wrapper. Now my workflow is: ``` wnew feat/login # creates worktree + cd into it # ...do work... wcd # fuzzy-pick another worktree, cd there wgo main # jump straight to main ``` Dashboard…
Jan 2026 · github.com
- 20DG
Devlog is a powerful tool that automatically generates (b)log posts from your Git commit history, providing a natural language summary of your development progress. It uses ollama to generate the blog posts locally so it never sends your data to third-party servers.
2024 · github.com
- 21
- 22GC
I built a tool which you can use to visualise your git commits at an org or repository level. It shows just how much work an engineering team, or even an individual does, that often goes unseen by non-dev teams. You can read about the build here: https://ably.com/blog/visualize-your-commits-in-realtime-wit... Repo is here: https://github.com/ably-labs/github-commit-visualizer You can deploy your own to netlify (or provider of your choice) and start visualising your own project's commits in realtime.
2022 · github-vis.ably.dev
- 23
- 24PT
I've been trying to figure out how long feature development takes, for years. I'm not a fan of (a priori) estimations of work, which just seem like the wrong measure. I think I've got a better way. Genuinely interested if some git gurus can improve this. Particularly around the pre-push hook, which is dependent on retained squash commit text. Or if there's an entirely better way to achieve the same thing.
2025 · doocot.sh
Ranked by how close each launch is in meaning, then by votes. Refine with a description →