Re:Ukrainian hackers destroyed the IT infrastructure of Russ...
by simonw on Wednesday July 16, 2025 @09:56AM
(#44582444)
I use GitHub Issues for this. It works so well - any time I make a decision I drop a comment on the relevant issue (often formatted as "Decision: ..."). Now they are archived, searchable, accessible via API and easy to navigate to from my source code because my commits all reference the issue number that relates to the change.
[ Parent
| on HN ]
Re:Ukrainian hackers destroyed the IT infrastructure of Russ...
by nchmy on Wednesday July 16, 2025 @11:47AM
(#44583591)
Til Github deletes your account randomly! Happened to a friend of mine recently, and he didn't get any explanation or recourse.
Of course, you have a relatively high profile, so could probably avoid it/get it reversed.
Re:Ukrainian hackers destroyed the IT infrastructure of Russ...
by sitkack on Wednesday July 16, 2025 @11:36AM
(#44583465)
What do you use for archiving github issues?
Re:Ukrainian hackers destroyed the IT infrastructure of Russ...
by tough on Wednesday July 16, 2025 @12:29PM
(#44584148)
you could just call the github API
Re:Ukrainian hackers destroyed the IT infrastructure of Russ...
by simonw on Wednesday July 16, 2025 @01:50PM
(#44585030)
I've tried a couple of things. I wrote a tool for exporting them to SQLite: https://github.com/dogsheep/github-to-sqlite
I've also tried a mechanism where I have GitHub Actions write them out as JSON files in the repo itself, then I can git clone them in one go: https://gist.github.com/simonw/0f906759afd17af7ba39a0979027a... and https://github.com/simonw/fetch-github-issues