 |
VOOZH | about |
|
VOOZH | about |
This version of GitHub Enterprise is discontinued as of December 12, 2018. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.
If you rewrite your commit history via git rebase or a force push, you may notice that your commit sequence is out of order when opening a pull request.
GitHub emphasizes Pull Requests as a space for discussion. All aspects of it--comments, references, and commits--are represented in a chronological order. Rewriting your Git commit history while performing rebases alters the space-time continuum, which means that commits may not be represented the way you expect them to in the GitHub interface.
If you always want to see commits in order, we recommend not using git rebase. However, rest assured that nothing is broken when you see things outside of a chronological order!
