delta/gitlab/gitlab-ce.git/doc/api, branch ci-https gitlab.com: gitlab-org/gitlab-ce.git Merge branch 'mahcsig/gitlab-ce-17350-multi-file-commit' 2016-10-06T11:41:16+00:00 Rémy Coutable remy@rymai.me 2016-10-06T11:41:16+00:00 5bdd8c3e3e7b94dab6dfe80a279764c4d451ca75 See !6096. 
See !6096.
multi-file commit 2016-10-05T17:42:52+00:00 Marc Siegfriedt marc@techaccelerator.com 2016-08-29T23:58:32+00:00 a1ee8cf5ad07256807f15590bdb5f56152d55553 add docs and tests - add additional validation allow move without content updated response 
add docs and tests - add additional validation
allow move without content
updated response
Added Issue Board API support 2016-10-05T16:12:07+00:00 Andre Guedes andrebsguedes@gmail.com 2016-10-03T03:12:59+00:00 41d70ea300efb73a05f4753ddd3e0c3730e96e0a - Includes documentation and tests 
  - Includes documentation and tests
Merge branch 'patch-6' into 'master' 2016-09-30T13:52:24+00:00 Dmitriy Zaporozhets dmitriy.zaporozhets@gmail.com 2016-09-30T13:52:24+00:00 9d48bace9b42eb8eac7d3d27a678da54364555a2 Fixed Session Cookie header ## What does this MR do? This MR fixes the wiki text header for the Session Cookie section ## Are there points in the code the reviewer needs to double check? It is markdown so probably not. Two very simple changes - first is replacing a dot with a space (was causing invalid markdown, not rendered as a header) and capitalized the word Cookie to match the other header formatting. ## Why was this MR needed? Fix the wiki documentation. ## Screenshots (if relevant) None. ## Does this MR meet the acceptance criteria? I can't imagine it wouldn't. - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [x] API support added - Tests - [x] Added for this feature/bug - [x] All builds are passing - [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? I didn't think this warranted an issue as it is just some simple wiki markdown formatting with little to no consequence. See merge request !6584 

Fixed Session Cookie header

## What does this MR do?

This MR fixes the wiki text header for the Session Cookie section

## Are there points in the code the reviewer needs to double check?

It is markdown so probably not. Two very simple changes - first is replacing a dot with a space (was causing invalid markdown, not rendered as a header) and capitalized the word Cookie to match the other header formatting.

## Why was this MR needed?

Fix the wiki documentation.

## Screenshots (if relevant)

None.

## Does this MR meet the acceptance criteria?

I can't imagine it wouldn't.

- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [x] API support added
- Tests
  - [x] Added for this feature/bug
  - [x] All builds are passing
- [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)

## What are the relevant issue numbers?

I didn't think this warranted an issue as it  is just some simple wiki markdown formatting with little to no consequence.

See merge request !6584
 Merge branch 'master' into 'fix_oauth_doc' 2016-09-30T12:58:41+00:00 Achilleas Pipinellis axilleas@axilleas.me 2016-09-30T12:58:41+00:00 91a91557ce4aeeafa34856009359bb6c34e3e10e # Conflicts: # doc/api/oauth2.md 
# Conflicts:
#   doc/api/oauth2.md
 Expose the Koding application settings in the API 2016-09-29T16:12:52+00:00 DJ Mountney david@twkie.net 2016-09-28T00:56:02+00:00 59157c0423d34c1f20c446548df540d103bda939 This will allow the Koding app to enable the integration itself once is has authorized an admin user using the application secrets. 
This will allow the Koding app to enable the integration itself once is has authorized an admin user using the application secrets.
Merge branch 'issue_22382' into 'master' 2016-09-29T13:04:16+00:00 Rémy Coutable remy@rymai.me 2016-09-29T13:04:16+00:00 f6a1a21f6f808738b3caccca1b1233303649f898 Expose project share expiration_date field on API closes #22382 See merge request !6484 

Expose project share expiration_date field on API

closes #22382

See merge request !6484
 Merge branch '22367-add-pipeline-id-build' into 'master' 2016-09-29T08:46:48+00:00 Rémy Coutable remy@rymai.me 2016-09-29T08:46:48+00:00 dbfcccaf7754d4501dc253b4409fc9f026248e67 Expose pipeline data in builds API Exposes pipeline data in builds API, as suggested by #22367. The fields exposed were 'id', 'status', 'ref', and 'sha'. Closes #22367 See merge request !6502 

Expose pipeline data in builds API

Exposes pipeline data in builds API, as suggested by #22367.
The fields exposed were 'id', 'status', 'ref', and 'sha'.

Closes #22367

See merge request !6502
 Fixed Session Cookie header 2016-09-29T05:07:17+00:00 Alan Moore kahunamoore@gmail.com 2016-09-29T05:07:17+00:00 6f1d243b998bfba6beedd0f7f6ff6ddb976a18c8 






expose pipeline data in builds API
2016-09-29T02:58:16+00:00

Guilherme Salazar
gmesalazar@gmail.com

2016-09-23T23:43:57+00:00

e80e4cb8b97a3865b7e3c551a856a53d98cccf75

add pipeline ref, sha, and status to the build API response

add tests of build API (pipeline data)

change API documentation for builds API

log change to builds API in CHANGELOG

CHANGELOG: add reference to pull request and contributor's name





add pipeline ref, sha, and status to the build API response

add tests of build API (pipeline data)

change API documentation for builds API

log change to builds API in CHANGELOG

CHANGELOG: add reference to pull request and contributor's name