+ [2016-10-09T21:49:16Z] Geo I guess thats a form of rebase as well, huh
+ [2016-10-09T22:58:32Z] dataangel I forked someone else's repository, cloned it, made a change and pushed. Then when I was making the pull request I realized I made a mistake. What is the correct workflow for changing my commit? If no one else commits to my fork, should I just amend locally and force push, or is there a better way?
+ [2016-10-09T23:18:20Z] milki dataangel: yes, amend and force push your branch
+ [2016-10-09T23:18:44Z] milki dataangel: updating your branch is how you update a pull request
+ [2016-10-09T23:38:28Z] dataangel milki: thanks

message no. 152989

Posted by Asido in #github at 2016-10-09T09:10:15Z

is it considered a good practice to split pull requests as much as possible? i.e. multiple bug fixes were fixed and I'd like to pull-request them. they are unrelated and would be reviewed independently. seems like a bad idea to send 1 pull-request for them
+ [2016-10-10T12:11:05Z] daleharvey I have a branch that requires review, I have review but needed to rebase and I want to push from the CL but gets rejected, is there any way around that?
+ [2016-10-10T12:12:16Z] Seveas push -f
+ [2016-10-10T12:21:41Z] daleharvey its a protected brranch, so no push -f
+ [2016-10-10T12:24:02Z] Seveas then push a new branch