delta/gitlab/gitlab-ce.git/lib/api/helpers, branch dm-diff-file-diffable gitlab.com: gitlab-org/gitlab-ce.git Refactor construction of response 2017-06-05T12:32:26+00:00 Michael Kozono mkozono@gmail.com 2017-05-23T18:34:58+00:00 b50a22894d4503cf99cecb8162696f854e1b3f85 






fix for Follow-up from "Backport of Multiple Assignees feature
2017-05-11T16:11:49+00:00

Valery Sizov
valery@gitlab.com

2017-05-08T14:58:42+00:00

22722659c233efb3b65bb35286ff07c192e3fc85












Merge branch '29925-gitlab-shell-hooks-can-no-longer-send-absolute-paths-to-gitlab-ce' into 'master'
2017-05-05T22:08:29+00:00

Sean McGivern
sean@mcgivern.me.uk

2017-05-05T22:08:29+00:00

9e041f2185ecb957e1f3d1205ea3bac54a5eb803

Generate and handle a gl_repository param to pass around components

Closes #29925

See merge request !10992




Generate and handle a gl_repository param to pass around components

Closes #29925

See merge request !10992






Backport of multiple_assignees_feature [ci skip]
2017-05-04T14:11:53+00:00

Valery Sizov
valery@gitlab.com

2017-05-04T12:11:15+00:00

387c4b2c21a44360386a9b8ce6849e7f1b8a3de9












Generate and handle a gl_repository param to pass around components
2017-05-03T20:37:30+00:00

Alejandro Rodríguez
alejorro70@gmail.com

2017-04-28T16:52:09+00:00

c45341c816d78d51aee84a6068d778b9cbc502c8

This new param allows us to share project information between components
that don't share or don't have access to the same filesystem
mountpoints, for example between Gitaly and Rails or between Rails and
Gitlab-Shell hooks. The previous parameters are still supported, but if
found, gl_repository is prefered. The old parameters should be deprecated
once all components support the new format.





This new param allows us to share project information between components
that don't share or don't have access to the same filesystem
mountpoints, for example between Gitaly and Rails or between Rails and
Gitlab-Shell hooks. The previous parameters are still supported, but if
found, gl_repository is prefered. The old parameters should be deprecated
once all components support the new format.







Remove unused user activities code
2017-04-14T13:20:55+00:00

Sean McGivern
sean@gitlab.com

2017-04-12T15:13:24+00:00

380e40fee30d836e6dffb1e956df39033d43a671












Remove user activities table and use redis instead of PG for recording activities
2017-04-14T13:20:55+00:00

James Lopez
james@jameslopez.es

2016-11-25T16:10:25+00:00

3cb84e06b7a118fb46b4e1e0d4885026c9d4a4d1

Refactored specs and added a post deployment migration to remove the activity users table.





Refactored specs and added a post deployment migration to remove the activity users table.







Set Git-specific env in /api/internal/allowed
2017-04-10T14:10:18+00:00

Rémy Coutable
remy@rymai.me

2017-04-05T07:29:30+00:00

710cd82cc16a9c67458c72ea6b2c4b676234ef79

Signed-off-by: Rémy Coutable <remy@rymai.me>





Signed-off-by: Rémy Coutable <remy@rymai.me>







Backport API changes needed to fix sticking in EE
2017-03-31T11:56:53+00:00

Yorick Peterse
yorickpeterse@gmail.com

2017-03-31T11:56:27+00:00

d2283f4f0e98b86800ba6a222593647e4991375d

These changes are ported over from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1502 to reduce
the number of merge conflicts that may occur.





These changes are ported over from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1502 to reduce
the number of merge conflicts that may occur.







Remove legacy Runners support in /api/v4/jobs/request
2017-03-20T08:40:36+00:00

Tomasz Maczukin
tomasz@maczukin.pl

2017-03-16T02:31:09+00:00

e79ab1115bf6ab4776678a379f7d507455d867c0

In Runner v1.3.0 we've started to send User-Agent header with Runner's
version data. Since GitLab v8.12.0 we've started to use this header to check
if used Runner's version supports 204 status code instead of 404 as a
response when there is no jobs to execute by a Runner.

In APIv4 (introduced in GitLab 9.0.0) will require Runner v9.0.0. And
writing more accurately: GitLab Runner v9.0.0 will require GitLab at
least 9.0.0. Because of such breaking change we are able to switch
entirely to 204 response code and there is no need to do check of
User-Agent.

This commit removes useless code and complexity.





In Runner v1.3.0 we've started to send User-Agent header with Runner's
version data. Since GitLab v8.12.0 we've started to use this header to check
if used Runner's version supports 204 status code instead of 404 as a
response when there is no jobs to execute by a Runner.

In APIv4 (introduced in GitLab 9.0.0) will require Runner v9.0.0. And
writing more accurately: GitLab Runner v9.0.0 will require GitLab at
least 9.0.0. Because of such breaking change we are able to switch
entirely to 204 response code and there is no need to do check of
User-Agent.

This commit removes useless code and complexity.