delta/gitlab/gitlab-ce.git/doc/api/projects.md, branch gitlab_shell_350 gitlab.com: gitlab-org/gitlab-ce.git The ID of a project can be also a string 2016-08-31T15:40:54+00:00 Achilleas Pipinellis axilleas@axilleas.me 2016-08-31T15:40:54+00:00 636dbc85e24600849de9dd09c4854edf4adfe807 [ci skip] 
[ci skip]
Renamed `enable_lfs` to `lfs_enabled` for the Project field, and related fixes. 2016-08-30T22:17:45+00:00 Patricio Cano suprnova32@gmail.com 2016-08-30T22:17:45+00:00 cf37d623e197dae5cc7efb021c1b1d85ca9674ee 






Added CHANGELOG, documentation, and API functionality
2016-08-30T21:17:41+00:00

Patricio Cano
suprnova32@gmail.com

2016-08-24T22:36:58+00:00

0227e98d0db2eb7fc6a35ddfcd3a0581ab550948












Merge branch 'patch-5' into 'master'

2016-08-30T19:09:06+00:00

Achilleas Pipinellis
axilleas@axilleas.me

2016-08-30T19:09:06+00:00

a5c1b42bf113c7a633eaeb51c998be58797d39dc


Update projects.md

## What does this MR do?
Repaired  some examples for a branches in projects.md

See merge request !6018





Update projects.md

## What does this MR do?
Repaired  some examples for a branches in projects.md

See merge request !6018






Mention that the `:id` of a project can also be `NAMESPACE/PROJECT_NAME`
2016-08-30T11:43:09+00:00

Achilleas Pipinellis
axilleas@axilleas.me

2016-08-30T11:43:09+00:00

8c101f9f860e03be20a90cafdcd19f897e47f62d

[ci skip]





[ci skip]







Update projects.md

2016-08-25T12:01:52+00:00

Miroslav Meca
miroslav.meca@profiq.cz

2016-08-25T12:01:52+00:00

01a1e3925acf01b925ad3b8ca370db30384111d8


The wrong example for "Branches".
Added option parameters in protect branch section.
Here is reason: https://gitlab.com/gitlab-org/gitlab-ee/commit/3ab07b8aae8dae43cfa3aae1306c59ea264a8594

Maybe this section could/should be deleted. Because in file repositories.md it had been deleted:  https://gitlab.com/gitlab-org/gitlab-ee/commit/8f3701eff005aeedcebff8ce02074f5056a369b3





The wrong example for "Branches".
Added option parameters in protect branch section.
Here is reason: https://gitlab.com/gitlab-org/gitlab-ee/commit/3ab07b8aae8dae43cfa3aae1306c59ea264a8594

Maybe this section could/should be deleted. Because in file repositories.md it had been deleted:  https://gitlab.com/gitlab-org/gitlab-ee/commit/8f3701eff005aeedcebff8ce02074f5056a369b3






Merge branch 'api_only_allow_merge_if_build_succeeds' into 'master'

2016-08-24T19:27:58+00:00

Douwe Maan
douwe@gitlab.com

2016-08-24T19:27:58+00:00

952c501fdf4a22e7ec06f825a36a4cbf5465d090


expose 'only_allow_merge_if_build_succeeds' project setting in the API

## What does this MR do?
Adds the 'only_allow_merge_if_build_succeeds' project setting in the API.

## Are there points in the code the reviewer needs to double check?
No, but maybe this code is not enough for ACLs or the like.

## Why was this MR needed?
Because that's a very useful setting to change via automation (through the API)

## What are the relevant issue numbers?

Closes #21085, closes https://gitlab.com/gitlab-org/gitlab-ce/issues/20088.

## Screenshots (if relevant)

## Does this MR meet the acceptance criteria?

- [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 [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)

See merge request !5930





expose 'only_allow_merge_if_build_succeeds' project setting in the API

## What does this MR do?
Adds the 'only_allow_merge_if_build_succeeds' project setting in the API.

## Are there points in the code the reviewer needs to double check?
No, but maybe this code is not enough for ACLs or the like.

## Why was this MR needed?
Because that's a very useful setting to change via automation (through the API)

## What are the relevant issue numbers?

Closes #21085, closes https://gitlab.com/gitlab-org/gitlab-ce/issues/20088.

## Screenshots (if relevant)

## Does this MR meet the acceptance criteria?

- [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 [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)

See merge request !5930






api: expose wiki_page_events project hook field in the API
2016-08-24T14:33:51+00:00

Ben Boeckel
ben.boeckel@kitware.com

2016-08-23T18:54:44+00:00

99c2f3b3c534386d1d8258fea23d3991695ff4fe












docs: document other project webhook fields
2016-08-24T14:33:37+00:00

Ben Boeckel
ben.boeckel@kitware.com

2016-08-23T18:51:05+00:00

f413d7ed8014601497834e5093a1892dd616875b












expose 'only_allow_merge_if_build_succeeds' project setting in the API
2016-08-24T08:11:48+00:00

Marc Dequènes (Duck)
duck@redhat.com

2016-08-22T03:47:58+00:00

31b2c1ef880349c9579f41e501de0346e59f0a4c