4 ms·

Not just Linux - most major open source projects I've come across on GitHub also practice similar processes, if not identical.

• vog 11y ago
  Unfortunately, GitHub pull requests encourage explicit merge commits for every pull request. This is not helpful and can be quite annoying - especially for pull requests that contain just a single commit. Those merge commits are introduced even if the Maybe there should be a GitHub feature that pull requests are automatically rebased (as long as possible safely and automatically). Or, that the GUI allows a pull reqeust to be "fast-forwarded" instead of "merged", if possible.
  • karyon 11y ago
    once more, gitlab does it right and offers a "rebase" button on merge requests along with a "fast-forward merges only" option for repositories. See http://doc.gitlab.com/ee/workflow/rebase_before_merge.html http://doc.gitlab.com/ee/workflow/rebase_before_merge.html
    • Zardoz84 11y ago
      I need to update or GitLab ...
    • vog 11y ago
      Not sure why this was downvoted. This is a really good point, and great to know!
    • ajdlinux 11y ago
      Huh, didn't know that - I'm starting to like GitLab more and more!
  • yxhuvud 11y ago
    Ideally it would be a setting on the repo to allow both kinds of processes.