-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub web UI: Force push timeline event #24401
Comments
it wasn't ever required to use fixup/squash commits. also its worth mentioning that at some point in the recent future, github review comments started persisting between force pushes, so it is technically possible to do a pr where you handle the whole review with force pushes. |
IIRC, I was asked to not force-push addressed comments in big diffs so that reviewers need not rescan all the diff to find what changed. |
Seems like this would solve that issue... Let's see how is the actual implementation affect our workflow.
Unless the code possession does not exist anymore (or does not fit some diff algorithm)
👍 |
Feel free to re-open if there's something specific we need to resolve. Otherwise, it seems like this can be closed? |
https://blog.github.com/changelog/2018-11-15-force-push-timeline-event/
Example: timeline event -> diff by
force-pushed
linkDoes this mean that we need not anymore create fixup commits for nit changes in big-diff-PRs to alleviate follow-up reviews?
The text was updated successfully, but these errors were encountered: