- 06 6月, 2017 1 次提交
-
-
由 Z.J. van de Weg 提交于
-
- 05 6月, 2017 1 次提交
-
-
由 Z.J. van de Weg 提交于
This is the first commit doing mainly 3 things: 1. create a new scope and allow users to use it 2. Have the JWTController respond correctly on this 3. Updates documentation to suggest usage of PATs There is one gotcha, there will be no support for impersonation tokens, as this seems not needed. Fixes gitlab-org/gitlab-ce#19219
-
- 27 5月, 2017 2 次提交
-
-
由 Clement Ho 提交于
-
由 Clement Ho 提交于
-
- 26 5月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 25 5月, 2017 5 次提交
-
-
由 Ruben Davila 提交于
There was a race condition issue when the application was generating an email and was using a language that was previously being used in other request.
-
由 Alexander Randa 提交于
* implemented logging of project and system web hooks * implemented UI for user area (project hooks) * implemented UI for admin area (system hooks) * implemented retry of logged webhook * NOT imeplemented log remover
-
由 Douwe Maan 提交于
This reverts commit b0498c17
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
-
- 24 5月, 2017 5 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 20 5月, 2017 2 次提交
-
-
由 Ruben Davila 提交于
-
由 Michael Kozono 提交于
In order to avoid string manipulation or modify route params (to make them unambiguous for `url_for`), we are accepting a behavior change: When being redirected to the canonical path for a group, if you requested a group show path starting with `/groups/…` then you’ll now be redirected to the group at root `/…`.
-
- 19 5月, 2017 4 次提交
-
-
由 Alexis Reigel 提交于
-
由 Michael Kozono 提交于
Don’t replace a substring of the path if it is part of the top level route. E.g. When redirecting from `/groups/ups` to `/groups/foo`, be careful not to do `/grofoo/ups`. Projects are unaffected by this issue, but I am grouping the `#ensure_canonical_path` tests similar to the group and user tests.
-
由 Oswaldo Ferreira 提交于
-
由 Michael Kozono 提交于
The host should not be modified, nor is it needed for the redirect.
-
- 18 5月, 2017 2 次提交
-
-
由 Yorick Peterse 提交于
This hides/disables some UI elements and API parameters related to nested groups when MySQL is used, since nested groups are not supported for MySQL.
-
由 Douwe Maan 提交于
-
- 17 5月, 2017 1 次提交
-
-
由 Z.J. van de Weg 提交于
Fixes gitlab-org/gitlab-ce#30814
-
- 15 5月, 2017 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 14 5月, 2017 2 次提交
-
-
由 Luke "Jared" Bennett 提交于
-
由 Douwe Maan 提交于
-
- 13 5月, 2017 3 次提交
-
-
由 Gabriel Mazetto 提交于
-
由 Sean McGivern 提交于
I don't know why this happens exactly, but given an upstream and fork repository from a customer, both of which required GC, resolving conflicts would corrupt the fork so badly that it couldn't be cloned. This isn't a perfect fix for that case, because the MR may still need to be merged manually, but it does ensure that the repository is at least usable. My best guess is that when we generate the index for the conflict resolution (which we previously did in the target project), we obtain a reference to an OID that doesn't exist in the source, even though we already fetch the refs from the target into the source. Explicitly setting the source project as the place to get the merge index from seems to prevent repository corruption in this way.
-
由 Pawel Chojnacki 提交于
-
- 12 5月, 2017 4 次提交
-
-
由 Michael Kozono 提交于
-
由 Pawel Chojnacki 提交于
- Tests for prometheus queries - fix rubocop warnings - Remove unused method. Add more queries to deployment queries. - Wrap BaseQuery in module hierarchy Renname Prometheus class to PrometheusClient
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Valery Sizov 提交于
-
- 11 5月, 2017 6 次提交
-
-
由 Douwe Maan 提交于
-
由 Sam Rose 提交于
-
由 Oswaldo Ferreira 提交于
-
由 Phil Hughes 提交于
-
由 Oswaldo Ferreira 提交于
-
由 Rémy Coutable 提交于
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: NRémy Coutable <remy@rymai.me>
-