3 ms·

Rebase (non-local rebase) based workflows are just awful. The best git methodology I've seen is (surprise, surprise) in the Linux kernel. I can keep everyones t

Rebase (non-local rebase) based workflows are just awful. The best git methodology I've seen is (surprise, surprise) in the Linux kernel. I can keep everyones tree as a separate tracking branch and use git work trees to develop against multiple branches on the same system. I also really enjoy using git request-pull, send-email, etc. and I think Github has been actively harmful in teaching people bad git habits.

sigmonsays 4y ago
any pointers on where to start for request-pull, send-email, etc. Ie, the linux kernel flow? Everything is a PR these days in github, so perhaps we find a way to do this with github.
- svmhdvn 4y ago
  A really good guide to learning this is https://git-send-email.io/ https://git-send-email.io/.
- tsegers 4y ago
  Sourcehut's tutorial on send-email is pretty good: https://git-send-email.io/ https://git-send-email.io/
account42 4y ago
Rebasing remote feature branches after feedback in the github-pull-request workflow is analogous to re-sending and updated patch series in the email workflow. The distinction shouldn't be if its remote or not but if its something "published" that others might build their work upon.