Force pushes can be disabled if you contact github support On Wed, Jul 22, 2015 at 11:14 PM, Gergo Tisza <[email protected]> wrote: > On Wed, Jul 22, 2015 at 4:39 AM, Petr Bena <[email protected]> wrote: > >> Good job, you aren't the only one. Huggle team is using it for quite >> some time. To be honest I still feel that github is far superior to >> our gerrit installation and don't really understand why we don't use >> it for other projects too. >> > > GitHub is focused on small projects; for a project with lots of patches and > committers it is problematic in many ways: > * poor repository management (fun fact: GitHub does not even log force > pushes, much less provides any ability to undo them) > * noisy commit histories due to poor support of amend-based workflows, and > also because poor message generation of the editing interface (Linus wrote > a famous rant > <https://github.com/torvalds/linux/pull/17#issuecomment-5654674> on that) > * no way to mark patches which depend on each other > * diff view works poorly for large patches > * CR interface works poorly for large patches (no way to write draft > comments so you need to do two passes; discussions can be marked as > obsolete by unrelated code changes in their vicinity) > * hard to keep track of cherry-picks > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
