Unclear error message when try publish package with not matching name and slug

[justgook]

You got message about fact you have not remote tag for your that suggest you to push tags to remote, even when there is already that tag.

{
... 
"name": "username/my-package"
}

but it lives in username/my-package-something-else

as result i got Error:

-- NO TAG ON GITHUB ------------------------------------------------------------

You have version 1.0.0 tagged locally, but not on GitHub.

Run the following command to make this tag available on GitHub:

    git push origin 1.0.0

This will make it possible to find your code online based on the version number.

That is totally wrong - as repo already have that tag. Maybe we could add validation about fact, that slug (username/repo) matches name in elm.json

[drathier]

Isn't it better to expand the error message to show e.g. if the repo exists at all, ask users to double-check the git url, and maybe print the tags it did find? The github api that the compiler uses to download code gives 404 for both wrong url and non-existant tag, so the compiler currently doesn't know which of those two error cases you hit, but it could print a hint.

[rlefevre]

Also I believe that the compiler does not know the actual repo name.
It could eventually compare the name in elm.json to some remote in .git/config remotes, but the logic to find the actual correct remote might not be trivial/robust as you can have several ones.