git history rewritten in the main "go" repo

[Brad Fitzpatrick]

Heads up: we've written the past 6 days of git history for https://github.com/golang/go/issues/28899 (a big binary was checked in 6 days ago)

If you use "git sync", this doesn't affect you. (I just checked)

If you don't use git sync, you presumably know how to use git, but this will blow away your local work and get you back on the train:

$ git fetch origin master && git reset --hard FETCH_HEAD
 

[Constantin Konstantinidis]

If your work is not on the master branch, you can rewrite before 50941e92414d5f51d1188285f593bfd8f6fbf515

>git reset --hard bfd9b94069e74b0c6516a045cbb83bf1024a1269

>git pull

[Brad Fitzpatrick]

And we just did it again for a separate CL.

Details in https://github.com/golang/go/issues/28962

Sorry.

We're re-prioritizing the tooling to prevent this from happening so easily.

In the meantime, everybody be extra vigilant (for now) when reviewing CLs adding new files. Gerrit will show the size of a new binary file at least, so review that line before giving your +2.  But relying on humans is never a strategy so automation will be the real answer. That is https://github.com/golang/go/issues/10658