yosh

@joshwnj I guess writing proper commits would be the way to go. I guess adding a backlog to every commit of all related discussion would wrk

@joshwnj e.g. when "closes GH-4" then does a scrape of the related issues and appends it to the end of the commit. Would that work?

@yoshuawuyts that's got some potential I think. Using the commit log like that, would there be an easy way to add notes retroactively?

@joshwnj git commit --amend ?

@yoshuawuyts that's only for rewriting the _last_ commit, right? Or is there a way to go further back?

@yoshuawuyts the case I have in mind is being able to trace from any part of a codebase, and ask "why did we decide do it this way?"

@joshwnj yeah, same here. GH issues would be another one; I work offline a lot and not having them fucks me over every time.

@yoshuawuyts seems there are some ways to get gh issues offline. But I also feel like these notes are branch-scope not repo-scope, do you?