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).
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!
Your personal site is a bit insane, but I love it. Great write up. And nice to see Elm still getting used.
The website is a reflection of the man https://taylor.town/ready-matters
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).
Should Archeologist rebase or merge when new evidence is undercover?
Can you give the use case? Or example runs? Seems like git log or git bisect should be enough?
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!
Great! AI crawlers would love this.