@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?
-
-
Replying to @yoshuawuyts
@yoshuawuyts that's got some potential I think. Using the commit log like that, would there be an easy way to add notes retroactively?1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts that's only for rewriting the _last_ commit, right? Or is there a way to go further back?2 replies 0 retweets 0 likes -
Replying to @joshwnj
@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?"1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@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?1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts yep, would be good to try! Only thought is whether that would be too fine-grained and fragment knowledge. Maybe feature-scope?2 replies 0 retweets 0 likes
@joshwnj which means branches are treated as features, which imo is more true, yeah
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.