- 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
-
- 16 Dec, 2016 2 commits
-
-
Timothy Andrew authored
- Don't define "allowed environment variables" in two places. - Dispatch to different arities of `Popen.open` without an if/else block. - Use `described_class` instead of explicitly stating the class name within a - spec. - Remove `git_environment_variables_validator_spec` and keep the validation inline.
-
Timothy Andrew authored
The list of environment variables in `Gitlab::Git::RevList` need to be validate to make sure that they don't reference any other project on disk. This commit mixes in `ActiveModel::Validations` into `Gitlab::Git::RevList`, and validates that the environment variables are on the level (using a custom validator class). If the validations fail, the force push is still executed without any environment variables set. Add specs for the validation using shared examples.
-