- 02 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 01 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 21 Jun, 2017 1 commit
-
-
Bob Van Landuyt authored
Otherwise we won't validate updates to the path. Allowing users to change the path to something that's not allowed.
-
- 30 May, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 24 May, 2017 3 commits
-
-
Douwe Maan authored
This reverts commit b0498c17
-
Douwe Maan authored
-
Douwe Maan authored
-
- 02 May, 2017 3 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
- 01 May, 2017 10 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
Reject the part following `/*namespace_id/:project_id` for paths containing 2 wildcard parameters
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
So we can block `objects` only when it is contained in `info/lfs` or `gitlab-lfs`
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
This reflects better that it validates paths instead of a namespace model
-
Bob Van Landuyt authored
The first part of a full path needs to be validated as a `top_level` while the rest need to be validated as `wildcard`
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
`Project` uses `ProjectPathValidator` which is now a `NamespaceValidator` that skips the format validation. That way we're sure we are using the same collection of reserved paths. I updated the path constraints to reflect the changes: We now allow some values that are only used on a top level namespace as a name for a nested group/project.
-
Bob Van Landuyt authored
-