Implement restriction of repo URL depth within hierarchical organisat… #680
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ion.
Brief:
With previous hierarchical style, if there is repo created within nested
projects, or better described as "subprojcts of subprojects", for user to
access it he needs to specify full blown URL to reach repos.
E.g repository: foo.git
http://redmine/projects1/project2/project3/project4/project5/foo.git
This patch implements same hierarchical style but with access to it
by only using <project_identifier>/repo.git
E.g
http://redmine/project5/foo.git