I don't think opening the browser, pasting a URL and pressing the fork button needs to be split into separate bullet points. Those are minuscule tasks. The real task is to edit the go.mod. You don't need to open go.mod and add the replace path manually. Just use go mod edit -replace=old=new for that.

The set of tasks basically are -

• fork the package
• go mod edit -replace=old=new
• Start building. (The updated go.mod will automatically fetch the new package)

To update your package, you need to git clone it obviously, but that is a separate workflow.

If/when your patch has been accepted upstream, just use go mod edit -dropreplace. I think this is smooth and simple. If you have any specific suggestions to improve this further, please feel free to open separate issues for those.

cc @bcmills @jayconrod in case I have missed something.

Thank you very much @agnivade, the go mod edit -replace=old=new / go mod edit -dropreplace workflow is perfect.