delta/gitlab/gitlab-ce.git - gitlab.com: gitlab-org/gitlab-ce.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	API: Expose branch statusapi-branch-status	Robert Schilling	2016-11-30	1	-1/+5
\|
*	Merge branch 'zj-expose-coverage-pipelines' into 'master'	Rémy Coutable	2016-11-25	1	-0/+1
\|\ \| \| \| \| \| \| \| \| \| \| \| \|	Expose coverage on GET pipelines/:id Closes gitlab-org/gitlab-ce#24801 See merge request !7670
\| *	Expose coverage on GET pipelines/:idzj-expose-coverage-pipelines	Z.J. van de Weg	2016-11-25	1	-0/+1
\| \| \| \| \| \| \| \| \| \|	The coverage wasn't exposed yet, now it is but only for detailed requests to save queries on the database.
* \|	Add a starting date to milestonesmilestone_start_date	Valery Sizov	2016-11-23	1	-0/+1
\|/
*	Remove default value for `project` argument on subscribable concern	Douglas Barbosa Alexandre	2016-11-17	1	-2/+2
\|
*	Pass project to Entities::Label to check if user is subscribed	Douglas Barbosa Alexandre	2016-11-17	1	-1/+1
\|
*	Merge branch 'fix_labels_api_adding_missing_parameter' into 'master'	Sean McGivern	2016-11-16	1	-1/+12
\|\ \| \| \| \| \| \| \| \|	fix labels API adding missing parameter (current_user) See merge request !7458
\| *	fix indentation	Francesco Coda Zabetta	2016-11-14	1	-7/+7
\| \|
\| *	fix labels API adding missing parameter (current_user)	Francesco Coda Zabetta	2016-11-14	1	-1/+12
\| \|
* \|	Issue #4270: Recursive option for files through API	Rebeca Méndez	2016-11-12	1	-1/+1
\|/
*	Expose Label id to API	Rares Sfirlogea	2016-11-07	1	-1/+1
\| \| \| \| \| \|	[e44da1c] Add Label API expected keys to tests [ac929c8] Update Label API documentation
*	Ability to update labels priority via API	Robert Schilling	2016-11-07	1	-0/+3
\|
*	Add setting to only allow merge requests to be merged when all discussions ↵	Rodolfo Santos	2016-11-04	1	-0/+1
\| \| \| \| \| \|	are resolved Signed-off-by: Rémy Coutable <remy@rymai.me>
*	Allow multiple repository storage shards to be enabled, and automatically ↵	Nick Thomas	2016-11-04	1	-0/+1
\| \| \| \|	round-robin between them
*	Merge branch 'zj-expose-system-hooks' into 'master'	Rémy Coutable	2016-11-03	1	-4/+3
\|\ \| \| \| \| \| \| \| \|	Expose more info for SystemHooks See merge request !6964
\| *	Update docs and unexpose token	Zeger-Jan van de Weg	2016-11-02	1	-1/+1
\| \|
\| *	Expose more data on the SystemHooks API	Z.J. van de Weg	2016-10-31	1	-4/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Now exposed: - push_events - tag_push_events - enable_ssl_verification - token Fixes gitlab-org/gitlab-ce#23307
* \|	Fix lightweight tags not processed correctly by GitTagPushService22271-drone-tag-pipeline-build	Alejandro Rodríguez	2016-10-28	1	-2/+2
\|/ \| \| \| \| \| \| \|	When we updated gitlab_git to 10.4.1, `tag.target` changed from pointing to the sha of the tag to the sha of the commit the tag points to. The problem is that only annotated tags have `object_sha`s, lightweight tags don't (it's nil), so (only) in their case we still need to use `tag.target`.
*	Added Issue Board API support	Andre Guedes	2016-10-05	1	-1/+17
\| \| \| \|	- Includes documentation and tests
*	Expose the Koding application settings in the APIkoding-setting-api	DJ Mountney	2016-09-29	1	-0/+2
\| \| \| \|	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'	Rémy Coutable	2016-09-29	1	-1/+1
\|\ \| \| \| \| \| \| \| \| \| \| \| \|	Expose project share expiration_date field on API closes #22382 See merge request !6484
\| *	Expose project share expiration_date field on APIissue_22382	Felipe Artur	2016-09-28	1	-1/+1
\| \|
* \|	expose pipeline data in builds API	Guilherme Salazar	2016-09-28	1	-2/+7
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 User#organization to users api	Dmitriy Zaporozhets	2016-09-27	1	-1/+1
\|/ \| \| \|	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
*	Merge branch '22065-group-members-api-returning-null-user-details' into ↵	Robert Speicher	2016-09-20	1	-3/+3
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	'master' Ensure invitees are not returned in Members API ## What are the relevant issue numbers? Closes #22065 See merge request !6370
\| *	Ensure invitees are not returned in Members API	Rémy Coutable	2016-09-16	1	-3/+3
\| \| \| \| \| \| \| \|	Signed-off-by: Rémy Coutable <remy@rymai.me>
* \|	Allow to set request_access_enabled for groups and projects using API	Felipe Artur	2016-09-19	1	-0/+2
\|/
*	Syntax fixes and better tests for helper methods. Updated docs.group-specific-lfs-settings	Patricio Cano	2016-09-15	1	-2/+4
\|
*	Added group-specific setting for LFS.	Patricio Cano	2016-09-15	1	-1/+1
\| \| \| \|	Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
*	Add notification_settings API calls	Marc Siegfriedt	2016-09-09	1	-1/+16
\| \| \| \|	Use NotificationSetting::EMAIL_EVENTS for params
*	Merge branch 'issue_19734' into 'master'	Douwe Maan	2016-09-01	1	-2/+10
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Project tools visibility level ## part of #19734 ![project_features_access_level](/uploads/81ec7185d4e61d7578652020209af925/project_features_access_level.png) ## 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 !5606
\| *	Project tools visibility level	Felipe Artur	2016-09-01	1	-2/+10
\| \|
* \|	Merge branch 'merge-request-sha-info' into 'master'	Douwe Maan	2016-09-01	1	-0/+2
\|\ \ \| \|/ \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Merge request sha info ## What does this MR do? Exposes `sha` and `merge_commit_sha` items in `MergeRequest` API endpoint data. ## Are there points in the code the reviewer needs to double check? No. ## Why was this MR needed? It's useful information. ## What are the relevant issue numbers? Closes #20456. ## Screenshots (if relevant) N/A ## 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 !5966
\| *	entities: expose {,merge_commit_}sha in MergeRequest	Ben Boeckel	2016-08-31	1	-0/+2
\| \| \| \| \| \| \| \|	Fixes #20456.
* \|	Add BroadcastMessage API implementation	Robert Speicher	2016-08-31	1	-0/+5
\| \|
* \|	API: Expose issue#confidentialapi-confidential-issues	Robert Schilling	2016-08-31	1	-0/+1
\|/
*	Renamed `enable_lfs` to `lfs_enabled` for the Project field, and related fixes.project-specific-lfs	Patricio Cano	2016-08-30	1	-1/+1
\|
*	Added CHANGELOG, documentation, and API functionality	Patricio Cano	2016-08-30	1	-1/+1
\|
*	Merge branch 'dz-merge-request-version'	Douwe Maan	2016-08-25	1	-0/+13
\|\
\| *	Fix merge request diff api	Dmitriy Zaporozhets	2016-08-22	1	-1/+1
\| \| \| \| \| \| \| \|	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
\| *	Merge branch 'master' into dz-merge-request-version	Dmitriy Zaporozhets	2016-08-22	1	-0/+4
\| \|\ \| \| \| \| \| \| \| \| \|	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
\| * \	Merge branch 'master' into dz-merge-request-version	Dmitriy Zaporozhets	2016-08-19	1	-4/+28
\| \|\ \ \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
\| * \ \	Merge branch 'master' into dz-merge-request-version	Dmitriy Zaporozhets	2016-08-15	1	-12/+14
\| \|\ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
\| * \| \| \|	Add single merge request diff API endpoint	Dmitriy Zaporozhets	2016-08-12	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
\| * \| \| \|	Add API to list merge request diff versions	Dmitriy Zaporozhets	2016-08-03	1	-0/+11
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* \| \| \| \|	Merge branch 'api_only_allow_merge_if_build_succeeds' into 'master'	Douwe Maan	2016-08-24	1	-0/+1
\|\ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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	Marc Dequènes (Duck)	2016-08-24	1	-0/+1
\| \| \| \| \| \|
* \| \| \| \| \|	Merge branch 'entity-api-web-url' into 'master'	Douwe Maan	2016-08-24	1	-0/+12
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	api: expose web_url for project entities ## What does this MR do? Adds a `web_url` field to project snippet, issues, and merge request API returned objects. ## Are there points in the code the reviewer needs to double check? Tests. Are they sufficient? (I'm working on getting them to pass.) ## Why was this MR needed? Creating the URL for an MR or issue from the MR is tedious in API libraries; it's easy for Gitlab to just provide it. ## What are the relevant issue numbers? N/A ## Screenshots (if relevant) N/A ## 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 !5631
\| * \| \| \| \| \|	api: expose web_url for project entities	Ben Boeckel	2016-08-24	1	-0/+12
\| \|/ / / / / \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This allows web hooks to have a URL back to entities without having to generate it themselves.
* \| \| \| \| \|	api: expose wiki_page_events project hook field in the API	Ben Boeckel	2016-08-24	1	-1/+1
\|/ / / / /