News for hackers. Stuff that matters.
Re:Successfully Merging the Work of 1000 Developers by byroot on Wednesday November 20, 2019 @12:56PM (#21586408)
It was tested. It's simply that between the time you pushed on your branch, and the time you merged, many other commits made it to the master branch, potentially breaking your branch.
Re:Successfully Merging the Work of 1000 Developers by pojzon on Wednesday November 20, 2019 @01:18PM (#21586674)
That pretty much forces tooling to try to rebase and run CI either way ? If it cannot rebase its up to the developer to fix his branch.

Master should be always in a state of release at any moment.

I just cannot imagine it was an unknown practice for some.

Re:Successfully Merging the Work of 1000 Developers by byroot on Wednesday November 20, 2019 @02:31PM (#21587530)
Except that with the amount of activity on the repo it's simply impossible.

Every new merge on master would require to rebase several hundred branches being worked on or awaiting reviewed. Multiply this with the hundreds of commits merged on master every day and you end up with way too much CI jobs to run.

Re:Successfully Merging the Work of 1000 Developers by pojzon on Thursday November 21, 2019 @01:15AM (#21591847)
Its not impossible.. thats what they ended up with either way.. And how do I know its possible ? Well I have over 2000 developers working on the same codebase in my current company. I work as a devops and this conversation is stupid..