delta/gitlab/gitlab-ce.git/doc/api, branch docs-pages-force-https gitlab.com: gitlab-org/gitlab-ce.git Merge branch '30355-use-hours-only-for-time-tracking' into 'master' 2019-06-25T07:58:26+00:00 Phil Hughes me@iamphill.com 2019-06-25T07:58:26+00:00 ed8605c42e46263d0aec58062ddd80f5511d0014 Limit time tracking units to hours Closes #30355 See merge request gitlab-org/gitlab-ce!29469 
Limit time tracking units to hours

Closes #30355

See merge request gitlab-org/gitlab-ce!29469
 Add Markdown linting 2019-06-25T04:34:55+00:00 Evan Read eread@gitlab.com 2019-06-25T04:34:55+00:00 e128239340010401b4e7fd391686dcc48c42fff0 Also adds and one linting rule and makes project conform to it. 
Also adds and one linting rule
and makes project conform to it.
Rename to time_tracking_limit_to_hours 2019-06-25T01:31:23+00:00 Heinrich Lee Yu heinrich@gitlab.com 2019-06-11T10:40:01+00:00 275a17589c2d468d8671a9f754a50b212273d509 Changes migration and all other places the attribute is used 
Changes migration and all other places the attribute is used
Limit time tracking values to hours 2019-06-25T01:31:23+00:00 Jon Kolb kolbyjack@gmail.com 2019-06-11T09:48:42+00:00 4e283ee706b11fd3b918230976addc9a70603ce6 Adds an instance setting to limit display of time tracking values to hours only 
Adds an instance setting to limit display of time tracking
values to hours only
Add name & search parameters to project environments API 2019-06-24T12:18:40+00:00 Lee Tickett lee@tickett.net 2019-06-24T12:18:40+00:00 ec66f1b5ca20764abe21524792480755b614dbc7 






Automatically update MR merge-ref along merge status
2019-06-20T14:48:30+00:00

Oswaldo Ferreira
oswaldo@gitlab.com

2019-05-21T21:14:22+00:00

3af348b6cf28ef1d9d3025f7012049132b57798c

This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.

In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.

We've also updated the logic to be more systematic and less user-based.





This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.

In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.

We've also updated the logic to be more systematic and less user-based.







Merge branch 'link_to_issue_statistics_api_endpoint_in_docs' into 'master'
2019-06-20T10:21:54+00:00

Achilleas Pipinellis
axil@gitlab.com

2019-06-20T10:21:54+00:00

4298a28a993363f4ab6b63c14820492393a3ae94

Docs: Link issue statistics api endpoint in the docs

See merge request gitlab-org/gitlab-ce!29855




Docs: Link issue statistics api endpoint in the docs

See merge request gitlab-org/gitlab-ce!29855






Update Docs for Container Registry API Delete Endpoints
2019-06-20T09:24:02+00:00

Jason Goodman
jgoodman@gitlab.com

2019-06-20T09:24:02+00:00

d29ba165593e38d05b0133a87e2b040094a875d0












Link issue statistics api endpoint in the docs
2019-06-20T09:02:12+00:00

Alexandru Croitor
acroitor@gitlab.com

2019-06-19T14:10:52+00:00

d18c101227878b6e451c241cfee5a12498a9067b

Adds the missing link to issues_statistics api endpoint





Adds the missing link to issues_statistics api endpoint







Updating CE repo to include new EE users API changes
2019-06-19T20:27:34+00:00

Michael Leopard
mleopard@gitlab.com

2019-06-19T20:27:34+00:00

8cf85b4bb50d0b116cb50699831f3ec049ae4ad4

Updated users API documentation
Moved API level changes to the service level





Updated users API documentation
Moved API level changes to the service level