-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support archives specified with basename param where files are in top level #36
Comments
Thanks @marcosbc for surfacing this issue. We will address this by proper handling of archives in the layout you describe, or with a better error message for an empty basename argument. If the user needs to rely on an basename argument specified but empty to control behaviour, that would be a misfeature we should address in some way that is more clear and the user intent explicit. Can you help me understand the issue better by describing the file name and layout location of a tarball containing Go code that you are trying to solve? Please include the location of |
You can find a couple of examples here with the Ingress Controller and Dashboard components. In the first case, the Please also note that, in both cases, it is discouraged to download the source code from GitHub since they consider it a non-official release site (example), so the only official tarballs are the ones provided in the download site. |
Another example of this would be https://github.com/openSUSE-zh/node-semver. I think it is quite common to have your |
We could use Edit: Writing this because this way we could stay backwards compatible. |
@SchoolGuy The issue mainly comes when the compressed archive does not include a basename. In the case of the application you mention, even though the go.mod is in the repository root, when you download the archive from GitHub, it will be inside the
However, there are other cases where this does not happen:
And those cases are the ones that do not work using |
@marcosbc Ah it seems after your hint I was able to get my |
When the basename option is specified with an empty value it is ignored and the default autodetection mechanism is used to look for a tarball. This issue is created to discuss the proposed change in PR #35.
This case happens when the application archive does not contain a basename at all. I.e., there isn't any folder in its root containing the rest of files:
The PR also identifies a couple of typos in related log lines:
The text was updated successfully, but these errors were encountered: