- 19 Jan, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 18 Jan, 2017 2 commits
-
-
Ruben Davila authored
New endpoints are: POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_estimate" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_time_estimate" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/add_spent_time" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_spent_time" GET :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_stats"
-
Grzegorz Bizon authored
If validation errors are present, include validation errors in the commit status API payload, instead of depending on state machine errors caused by invalid record.
-
- 16 Jan, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 15 Jan, 2017 2 commits
-
-
Robert Schilling authored
-
Bruno Melli authored
-
- 12 Jan, 2017 3 commits
-
-
David Eisner authored
- Use IssuesFinder for the /issues API resouce - Tests for iid filter in project issues API resource - Tests for No Milestone filter in issues API resources The "No Milestone" case was not previously tested, and the `/issues` resource did not support the the `milestone` parameter. - Return issues where all labels match from the issues and project issues API resources, like the group issues resource already does. See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6825#note_17474533Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Panagiotis Atmatzidis authored
Current filtering for "/projects/:id/issues" endpoint returns no results for "No Milestone" query. This PR introduces fix by copying filtering from "/groups/:id/issues" which works as expected.
-
Horacio Sanson authored
This MR enables rendering of PlantUML diagrams in Asciidoc documents. To add a PlantUML diagram all we need is to include a plantuml block like: ``` [plantuml, id="myDiagram", width="100px", height="100px"] -- bob -> alice : ping alice -> bob : pong -- ``` The plantuml block is substituted by an HTML img element with *src* pointing to an external PlantUML server. This MR also add a PlantUML integration section to the Administrator -> Settings page to configure the PlantUML rendering service and to enable/disable it. Closes: #17603
-
- 11 Jan, 2017 1 commit
-
-
Mark Fletcher authored
-
- 09 Jan, 2017 1 commit
-
-
Rémy Coutable authored
Fixes #26051. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 08 Jan, 2017 1 commit
-
-
Vincent Wong authored
Addresses: Issue #13810 1. Adds a last_used_at attribute to the Key table/model 2. Update a key's last_used_at whenever it gets used 3. Display how long ago an ssh key was last used
-
- 05 Jan, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 04 Jan, 2017 3 commits
-
-
Lin Jen-Shin authored
* We realized that headers were not set whenever we give 204 because `render_api_error!` doesn't preserve the headers. * We also realized that `update_runner_info` would be called in POST /builds/register every time therefore runner is updated every time, ticking the queue, making this last_update didn't work very well, and the test would be failing due to that.
-
Robert Schilling authored
-
Robert Schilling authored
-
- 03 Jan, 2017 5 commits
-
-
Robert Schilling authored
-
Z.J. van de Weg authored
-
Mark Fletcher authored
* Use standard helpers for finding group and project
-
Robert Schilling authored
-
Mark Fletcher authored
-
- 29 Dec, 2016 1 commit
-
-
Robert Schilling authored
-
- 28 Dec, 2016 1 commit
-
-
Robert Schilling authored
-
- 23 Dec, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 22 Dec, 2016 1 commit
-
-
Robert Schilling authored
-
- 21 Dec, 2016 4 commits
-
-
Markus Koller authored
This adds counters for build artifacts and LFS objects, and moves the preexisting repository_size and commit_count from the projects table into a new project_statistics table. The counters are displayed in the administration area for projects and groups, and also available through the API for admins (on */all) and normal users (on */owned) The statistics are updated through ProjectCacheWorker, which can now do more granular updates with the new :statistics argument.
-
Markus Koller authored
-
Markus Koller authored
-
Grzegorz Bizon authored
[ci skip]
-
- 20 Dec, 2016 6 commits
-
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Hiroyuki Sato authored
-
Hiroyuki Sato authored
-
Hiroyuki Sato authored
-
- 19 Dec, 2016 2 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Kamil Trzcinski authored
-
- 18 Dec, 2016 1 commit
-
-
Arsenev Vladislav authored
-
- 16 Dec, 2016 1 commit
-
-
Timothy Andrew authored
1. Starting version 2.11, git changed the way the pre-receive flow works. - Previously, the new potential objects would be added to the main repo. If the pre-receive passes, the new objects stay in the repo but are linked up. If the pre-receive fails, the new objects stay orphaned in the repo, and are cleaned up during the next `git gc`. - In 2.11, the new potential objects are added to a temporary "alternate object directory", that git creates for this purpose. If the pre-receive passes, the objects from the alternate object directory are migrated to the main repo. If the pre-receive fails the alternate object directory is simply deleted. 2. In our workflow, the pre-recieve script (in `gitlab-shell) calls the `/allowed` endpoint, which calls out directly to git to perform various checks. These direct calls to git do _not_ have the necessary environment variables set which allow access to the "alternate object directory" (explained above). Therefore these calls to git are not able to access any of the new potential objects to be added during this push. 3. We fix this by accepting the relevant environment variables (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the `/allowed` endpoint, and then include these environment variables while calling out to git. 4. This commit includes (whitelisted) these environment variables while making the "force push" check. A `Gitlab::Git::RevList` module is extracted to prevent `ForcePush` from being littered with these checks.
-