On Wed, Jul 26, 2017 at 12:09 PM, Jonah Graham <[email protected]> wrote:
> However, be careful with doing force pushes on GitHub, you can lose > some/all of the review history. That is the main reason I like doing > Squash and Merge. > I have to admit I sometimes make mistake with a Git push force ;) However, as the local Git repo keeps the reflog for a while, it has always been easy to push back the correct history to a branch. A basic rule to follow would be to never push --force on the "official" repo and to allow yourself that on your fork, that covers well the use-case of Gerrit-ifying the GitHub PR workflow with updates of a single commit rather than a sequence. -- Mickael Istria Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/> developer, at Red Hat Developers <https://developers.redhat.com/> community
_______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation
