34 points surprisetalk | 8 comments | | HN request time: 0.932s | source | bottom

Hello friends,

Today I'm sharing a little tool to help you explore GitHub repositories:

https://diggit.dev

This project was admittedly a big dumb excuse to play with Elm and Claude Code. I published my design notes and all the chat transcripts here:

https://taylor.town/diggit-000

Please add bug reports and feature requests to the repo:

https://github.com/surprisetalk/diggit

Enjoy!

1. personjerry ◴[] No.45029809[source]
Can you give the use case? Or example runs? Seems like git log or git bisect should be enough?
replies(1): >>45030253 #
2. dinkleberg ◴[] No.45030207[source]
Your personal site is a bit insane, but I love it. Great write up. And nice to see Elm still getting used.
replies(1): >>45039027 #
3. surprisetalk ◴[] No.45030253[source]
git log is probably good enough for 90% of folks :)

The main reason I wanted to build this is that git log doesn't give me context from GitHub PRs/issues/milestones or CI events. When I'm diving into a new codebase, I like to see who's been working on what, and what ongoing problems/initiatives are propelling that development.

I've only got GH issues up (not milestones or CI events yet), but I think this is a good start!

4. ATechGuy ◴[] No.45030830[source]
Great! AI crawlers would love this.
5. kylemaxwell ◴[] No.45030964[source]
I got all excited thinking this was related to real-world archaeology and somehow providing a git-like representation of that. (No idea how it would work, which is why I was excited).
replies(1): >>45035864 #
6. DHRicoF ◴[] No.45035864[source]
Should Archeologist rebase or merge when new evidence is undercover?
7. high_priest ◴[] No.45039027[source]
The website is a reflection of the man https://taylor.town/ready-matters