News for hackers. Stuff that matters.
Re:Test && commit || revert by jrockway on Friday September 28, 2018 @08:20PM (#18098015)
I think PRs are logically the same as Perforce changelists. The fact that you can pick apart a PR into multiple commits does pollute the history when you merge, though, unless your tools treat the PR as a single atomic commit (for bisection, etc.)

I have never treated the individual commits inside a PR as anything other than "I'd like to backup my workstation to the cloud now", but if people are treating them as something meaningful, I think that's a mistake.

Re:Test && commit || revert by int0x80 on Saturday September 29, 2018 @02:41AM (#18099039)
I don't know if I'm reading your comment correctly, sorry if I'm not... but individual commits within a PR are absolutely not a backup. Every commit in the PR has to be a logical unit, meaningful, atomic and stand on its own. The PR, as a high level feature, is just a grouping. But single commits have to be useful and be a history/build up of how high level features are being developed. This granularity is important to logically isolate the changes and make them bisectable among other things.
Re:Test && commit || revert by XorNot on Saturday September 29, 2018 @12:08AM (#18098655)
The popularity of rebase merging in Git I think is partly to blame here. Rebase merging tries to make everything seem like real history, but no one ever seems to have a solid idea of what that actually is supposed to mean (and CI systems don't make it easy to configure "test all commits" or declare what you want your commit history to mean).
Re:Test && commit || revert by Vinnl on Saturday September 29, 2018 @06:57AM (#18099741)
There's no such thing as "real history" - even without rebasing, your commits do not reflect the development of the code; they reflect practically arbitrary moments in time at which you chose to commit.

The idea behind rebasing is not to make it seem like "real history", but to have all changes in a commit to be related. They're not a reflection of how you built the code, but how you can understand it. They're documentation, and as such, you spend effort on them.

Re:Test && commit || revert by jrockway on Saturday September 29, 2018 @12:42AM (#18098748)
Yup. I always picked "merge" instead of "rebase" in Gerrit because it's not like I tested the result of applying each patch to the master branch. All I did was decide that mine worked and that I wanted to merge my branch with the upstream.

People like using clever features to make the history inaccurate, which seems like a bad idea to me. (It's "cleaner", but wrong.)

Re:Test && commit || revert by int0x80 on Saturday September 29, 2018 @02:44AM (#18099043)
If you internally rebase to cleanup history you have to test again. Ignoring that step is wrong. Local rebase can be good and useful.