bundle can handle this edge-case better by deduplicating identical imports.

When a given import path is loaded twice:

import (
	"same/import/path"
	a "same/import/path"
)

It would need to load the package with import path "same/import/path" and find out the package name. If the name the same, then one of those imports can be safely dropped.

Note that the package name is not always equal to the last path element of its import path. For example:

import (
	"github.com/micro/go-micro"
	micro "github.com/micro/go-micro"
)

Those two imports are identical despite "micro" not being the same as the last import path element, and should still be deduplicated.

However, it would be invalid to deduplicate two imports when the package name is different from the renamed one.

I have a patch for this. What would be the best way to contribute this? I'm building on top of an existing CL. @dmitshur

@meling The best way would be to send a GitHub PR or Gerrit CL. Take a look at https://golang.org/doc/contribute.html#sending_a_change_github and https://golang.org/doc/contribute.html#sending_a_change_gerrit where the two options are described.

Building on top of an existing CL should be more achievable via Gerrit. You can just rebase your commit on top of the commit corresponding to the existing CL, and git codereview mail should work to create a new CL corresponding to your own commit. (Although I haven't tried to do this using someone else's existing CL, so I can't guarantee it'll work.)

Change https://golang.org/cl/222997 mentions this issue: cmd/bundle: de-duplicating identical imports