(diggit.dev)

34 points surprisetalk | 1 comments | 25 Aug 25 11:42 UTC | HN request time: 0.001s | source

Hello friends,

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

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!

Show context

personjerry ◴[26 Aug 25 17:40 UTC] No.45029809[source]▶

>>45012776 (OP) #

Can you give the use case? Or example runs? Seems like git log or git bisect should be enough?

replies(1): >>45030253 #

1. surprisetalk ◴[26 Aug 25 18:16 UTC] No.45030253[source]▶

>>45029809 #

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!

↑

Show HN: Diggit.dev – Git history for architecture archaeologists