The download link just moved in the new Gerrit UI. It's now above the list of changed files:

There might be something to do here but I'm apprehensive about adding even more stuff to our contribution guide about using git. We did that at first and we've been trying to undo the damage ever since. It's hard enough to find the Go-specific information in that document.

Thanks for showing me where it is. I missed that.

I understand the apprehension concerning writing a full git tutorial. I do think at least it would be useful to update with the new Gerrit API and moving the section to a more visible location (for those who are asked to apply patches but haven't contributed to Go).

The motivation for the third bullet is that I was unsure how changes would be applied relative to tip. For example, do I need to be on a specific version of tip to correctly apply the patch? If the provided fetch command through "Checkout" will work as desired in most cases, then I don't think there is any need to further update the documentation.

The motivation for the third bullet is that I was unsure how changes would be applied relative to tip.

Even if we document something (cherry-pick vs checkout), empirically it seems like it'll be wrong about half the time. When I see discussions on bugs or CLs requesting users try a CL, half the time it's "try this exact commit" (git checkout) but half the time it's "try this on along with your local change" (cherry-pick).

And when we're asking people to do that, they're generally developers. If we want users to test something we generally submit it and add some temporary knob (GODEBUG, etc).