- 01 May, 2017 12 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
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
-
Bob Van Landuyt authored
So we can use it for projects
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
This reflects better that it validates paths instead of a namespace model
-
Bob Van Landuyt authored
Since the namespacevalidator now knows the difference between a top-level and another path, this could all be handled there.
-
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.
-
- 29 Apr, 2017 1 commit
-
-
Stan Hu authored
This reverts merge request !10845
-
- 27 Apr, 2017 8 commits
-
-
Tiago Botelho authored
-
Douwe Maan authored
-
Timothy Andrew authored
- We upgraded `rugged` to 0.25.1.1 in !10286 for %9.1 - Prior to this upgrade, the default sort order for commits returned by `Gitlab::Git::Repository#find_commits` was `Rugged::SORT_DATE`, which the graph relied on. - While upgrading `rugged`, the MR also changed this default to `Rugged::SORT_NONE`, which broke commit ordering in the graph. - This commit adds an option to `Gitlab::Git::Repository#find_commits` to sort by date, and changes the graph builder `Network::Graph` so it explictly requests the `:date` sort order
-
Toon Claes authored
-
Douwe Maan authored
-
Toon Claes authored
Because the post-processing of the rendered README is dependent on the context (i.e. the current user), do the post-processing when the README is being displayed.
-
Toon Claes authored
TodoService should not call `.select(&:id)` on todos, because this is bad performance. So instead use sub-queries, which will result in a single SQL query to the database. https://docs.gitlab.com/ee/development/sql.html#plucking-ids
-
Luigi Leoni authored
-
- 26 Apr, 2017 10 commits
-
-
Douglas Barbosa Alexandre authored
-
Zeger-Jan van de Weg authored
-
Jacob Vosmaer authored
-
Bob Van Landuyt authored
-
Maxim Rydkin authored
-
Maxim Rydkin authored
-
Timothy Andrew authored
- Currently, (for example) admins can't delete snippets for blocked users, which is an unexpected limitation. - We modify `authenticate!` to conduct the `access_api` policy check against the `initial_current_user`, instead of the user being impersonated. - Update CHANGELOG for !10842
-
Lin Jen-Shin authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
- 25 Apr, 2017 9 commits
-
-
Jeff Stubler authored
-
Douglas Barbosa Alexandre authored
-
Robert Schilling authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Lin Jen-Shin authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-