+ [2016-07-24T21:43:04Z] nedbat rrva: does github have any reformatters?
+ [2016-07-24T21:43:09Z] rrva no
+ [2016-07-24T21:43:15Z] Zarthus rrva: do you want something like a CI?
+ [2016-07-24T21:44:36Z] rrva ideally, i'd like something like the parameter &w=1 used to do (ignore whitespace diffs), but "ignore reformatting diffs". I know that's difficult to achieve, but any workaround for faster reviewing of pull requests which contain both reformatting and other changes mixed in the same pr is wanted.
+ [2016-07-24T21:45:15Z] rrva like this about &w=1 https://github.com/blog/967-github-secrets

message no. 144365

Posted by rrva in #github at 2016-07-24T21:42:05Z

if I have some commits which introduce a lot of code-reformatting mixed with functional changes, is there some standard way of running the reformatter on the code prior to the commit to only see the functional diffs?
+ [2016-07-25T04:38:21Z] SlizardWizard Hi, is it possible to revert a commit after creating a new branch?
+ [2016-07-25T04:43:20Z] SlizardWizard For example, i had made some changes to some files which broke everything. I commited them to master. I now have to fix a bug on the release version. So i created a new branch called "release" and i want to revert the last couple commits just on that branch to get the code back to working state
+ [2016-07-25T04:43:50Z] SlizardWizard I understand in the future i shouldn't commit to master when working on broken stuff but i still need to fix this issue now
+ [2016-07-25T05:10:31Z] deltab SlizardWizard: switch to the release branch, then git reset HEAD~2 or whichever the last commit you want is
+ [2016-07-25T05:12:34Z] deltab see "Undo a commit, making it a topic branch" in the man page for git-reset