- 07 Nov, 2016 2 commits
-
-
Rares Sfirlogea authored
[e44da1c] Add Label API expected keys to tests [ac929c8] Update Label API documentation
-
Robert Schilling authored
-
- 04 Nov, 2016 2 commits
-
-
Rodolfo Santos authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Nick Thomas authored
-
- 02 Nov, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 01 Nov, 2016 2 commits
-
-
Sean McGivern authored
-
Gauvain Pocentek authored
The UI allows to define a token to validate payload on the target URL, this patch adds the feature to the API.
-
- 31 Oct, 2016 1 commit
-
-
Z.J. van de Weg authored
Now exposed: - push_events - tag_push_events - enable_ssl_verification - token Fixes gitlab-org/gitlab-ce#23307
-
- 28 Oct, 2016 1 commit
-
-
Alejandro Rodríguez authored
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`.
-
- 05 Oct, 2016 1 commit
-
-
Andre Guedes authored
- Includes documentation and tests
-
- 29 Sep, 2016 2 commits
-
-
DJ Mountney authored
This will allow the Koding app to enable the integration itself once is has authorized an admin user using the application secrets.
-
Guilherme Salazar authored
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
-
- 28 Sep, 2016 1 commit
-
-
Felipe Artur authored
-
- 27 Sep, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 19 Sep, 2016 1 commit
-
-
Felipe Artur authored
-
- 16 Sep, 2016 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 15 Sep, 2016 4 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
-
Patricio Cano authored
-
Patricio Cano authored
- Required on the GitLab Rails side is mostly authentication and API related.
-
- 09 Sep, 2016 1 commit
-
-
Marc Siegfriedt authored
Use NotificationSetting::EMAIL_EVENTS for params
-
- 01 Sep, 2016 1 commit
-
-
Felipe Artur authored
-
- 31 Aug, 2016 3 commits
-
-
Robert Speicher authored
-
Ben Boeckel authored
Fixes #20456.
-
Robert Schilling authored
-
- 30 Aug, 2016 2 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
- 24 Aug, 2016 3 commits
-
-
Ben Boeckel authored
-
Ben Boeckel authored
This allows web hooks to have a URL back to entities without having to generate it themselves.
-
Marc Dequènes (Duck) authored
-
- 23 Aug, 2016 1 commit
-
-
Ben Boeckel authored
-
- 22 Aug, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 18 Aug, 2016 6 commits
-
-
Sean McGivern authored
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
- 16 Aug, 2016 2 commits
-
-
Timothy Andrew authored
1. Change a few incorrect `access_level` to `access_levels.first` that were missed in e805a647. 2. `API::Entities` can iterate over all access levels instead of just the first one. This makes no difference to CE, and makes it more compatible with EE.
-
Timothy Andrew authored
!581 has a lot of changes that would cause merge conflicts if not properly backported to CE. This commit/MR serves as a better foundation for gitlab-org/gitlab-ee!581. = Changes = 1. Move from `has_one {merge,push}_access_level` to `has_many`, with the `length` of the association limited to `1`. This is _effectively_ a `has_one` association, but should cause less conflicts with EE, which is set to `has_many`. This has a number of related changes in the views, specs, and factories. 2. Make `gon` variable loading more consistent (with EE!581) in the `ProtectedBranchesController`. Also use `::` to prefix the `ProtectedBranches` services, because this is required in EE. 3. Extract a `ProtectedBranchAccess` concern from the two access level models. This concern only has a single `humanize` method here, but will have more methods in EE. 4. Add `form_errors` to the protected branches creation form. This is not strictly required for EE compatibility, but was an oversight nonetheless.
-