-
Notifications
You must be signed in to change notification settings - Fork 153
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
Unable to install_gitlab
repos within subgroups
#259
Comments
I was not aware of this subgroup concept, looking at this example I am not really sure how it could be supported while also retaining support for subdirectories |
Please see #308 – quick and dirty workaround. |
Any chance we can re-start the conversation on installing from sub groups? We're considering moving our github/USGS-R packages to a sub group. Here's an example: The subgroup: The repo: For the record, this works: remotes::install_git("https://code.usgs.gov/water/stats/MGBT.git")
remotes::install_url("https://code.usgs.gov/water/stats/MGBT/-/archive/master/MGBT.zip") So...maybe we just need to get people to use that... |
If we want to use
install_gitlab
we supply arepo
parameter which is inusername/repo[/subdir][@ref]
format. This string is split by parse_repo_spec so we have ausername
variable (e.g., "r-lib") andrepo
variable (e.g., "remotes").If my repo is within a GitLab group, then I can simply replace the
username
portion of therepo
parameter with the name of the group.However, if I have a subgroup holding the repo, I'm stuck. There is no
params
variable for subgroups.There is no way to get the subgroup past the
parse_repo_spec
function. So, further functions that stick the URL back together do it incorrectly. The URL in the error above should be,https://gitlab.com/timtrice_tests/tests/raw/master/falsy/DESCRIPTION?private_token=ABCDEFGHIJKLMNOP
For example, in
remote_package_name
, the src is built (usingbuild_url
) as that in the error message. But, if I change src to the last example above, while debugging, it is successful.Another option is, instead of using the group/subgroup/repo combination, perhaps we can pass the Project ID? This doesn't seem to work in
remote_pacage_name
but it does ingitlab_commit
.The text was updated successfully, but these errors were encountered: