-
Notifications
You must be signed in to change notification settings - Fork 240
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
fix: #479 allow nested repos for gitlab.com #494
base: main
Are you sure you want to change the base?
fix: #479 allow nested repos for gitlab.com #494
Conversation
b1ac42c
to
a76aa0f
Compare
a76aa0f
to
5515e0a
Compare
Could we get someone to review this change, please? |
…-subpath-query fix: hashicorp#479 allow nested repos for gitlab.com
rebase or main repo
b92f938
to
83ccf98
Compare
I am not sure why I am only now seeing this notification in GitHub, but I will raise this in triage. I find this comment interesting, gruntwork-io/terragrunt#3031 (comment), will see what is underneath that difference. To set expectations, there is a strong headwind to getting PRs reviewed and merged into this repo due to multiple products using it and an unwillingness to inadvertently add new bugs. In any case, thanks for the submission! |
Address #479
As per GitLab documentation, repositories can be nested under projects and subgroups: https://docs.gitlab.com/ee/user/group/subgroups/
MR is to remove the limit of 3 components of the path (gitlab.com/username/repo) and allow referencing paths to directories inside the repo.
Parse must be performed on the whole URL before evaluating and adding the .git suffix to the repo name to keep the ref query in its original format (?ref=master vs %3Fref=master if parsed as a part of the path).