Hi friends. I'm curious how you all use GitHub's blame page. Help me out with this (literally) 1 minute survey?
https://goo.gl/forms/K2EiijjOAJ6UR7F02 …
-
-
Replying to @brianmario
I would like to expand on my answer to "How often do you want to open the PR that included the line's last commit?" b/c 1 doesn't cut it
1 reply 0 retweets 0 likes -
Replying to @sgrif @brianmario
Never because I want all the relevant context in the commit message
1 reply 0 retweets 0 likes -
Replying to @sgrif
What if that code changes after that commit, and is thus out of date but before the pull request is merged?
2 replies 0 retweets 0 likes -
Replying to @brianmario
But generally if there was any significant discussion during code review I will rebase and include in the commit message
1 reply 0 retweets 0 likes -
Replying to @sgrif
I see. Yeah a rebasing workflow would definitely allow for "correcting" things after the fact like that. But for always fwd moving pulls...
1 reply 0 retweets 0 likes -
Replying to @brianmario
Doesn't even have to be a workflow. The big green button can literally do it for you, and lets you specify the commit message
1 reply 0 retweets 0 likes -
Replying to @sgrif @brianmario
In my experience if I *really* need the PR, it's always linked to from the commit page, but I want to never really need it
1 reply 0 retweets 1 like -
Replying to @sgrif
Cool, thank you so much for the feedback! Really appreciate it :)
1 reply 0 retweets 0 likes
No problem. Sorry for spamming your mentions. Blame is probably my single most used tool and I have really strong opinions about it XD
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.