Add triggers API
References #4264 (closed)
Merge request reports
Activity
mentioned in issue #4264 (closed)
Added 1 commit:
- 30985008 - Fix ci_trigger_request factory
Added 1 commit:
- 86756646 - Get show details feature to triggers API
@ayufan I think that this feature is ready for review
Added 1 commit:
- b0a77a22 - Update ./doc/api
Added 1 commit:
- e0ec69d9 - Change 'trigger_id' to 'token' as resource ID in triggers API
@DouweM @rspeicher Can you review?
Added 1 commit:
- d44653da - Add some fixes after review
Check @axil's ongoing documentation styleguide MR and make sure these API docs conform to the standard.
Added 440 commits:
-
d44653da...0e344aa2 - 437 commits from branch
master
- 6201a5dd - Merge branch 'master' into ci/api-triggers
- a31bd940 - Modify triggers API documentation style [ci skip]
- 58b7ce65 - Update CHANGELOG {ci skip]
Toggle commit list-
d44653da...0e344aa2 - 437 commits from branch
@DouweM @rspeicher: Triggers entry in API documentation index prefixed, documentation style changed. CHANGELOG updated.
If there are no more comments, then ready for merging :)
Copying from my comment in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2264#note_3199256
Some general advice (which I forgot to document, so it's my fault):
Do not add headings for
Parameters
,Example of request
andExample of response
, add only for the main calls. Always imagine that the headings end up being referenced in doc.gitlab.com. How would you know what is referenced if your URL isapi/build_variables.md#parameters
? If you have multiple times the same heading you would not know where to go.Other than that I'll leave some inline comments.
- doc/api/build_triggers.md 0 → 100644
Added 6 commits:
- 99393cde - Version 8.4.0.rc1
- d139276a - Merge branch 'master' into 8-4-stable
- 633ac134 - Modify triggers API documentation style [ci skip]
- 57a67c4f - Merge branch '8-4-stable' into ci/api-triggers
- d8359a4f - Update CHANGELOG [ci skip]
- c5b429f0 - Add mofications to triggers API documentation [ci skip]
Toggle commit list@axil: documentation is fixed
@rspeicher @DouweM: if there are no more comments, then ready to be merged. As we agreeded with Robert, the MR is pointing to
8-4-stable
. After merge it should be picked tomaster
.Edited by Tomasz MaczukinAdded 41 commits:
-
c5b429f0...4d64a32c - 39 commits from branch
master
- 8eed1876 - Merge branch 'master' into ci/api-triggers
- 41eedd45 - Fix version
-
c5b429f0...4d64a32c - 39 commits from branch
@DouweM: target branch switched back to
master
. All conflicts resolved.Enabled an automatic merge when the build for 41eedd45 succeeds
Added 24 commits:
-
41eedd45...f981da44 - 22 commits from branch
master
- af3b97cd - Merge branch 'master' into ci/api-triggers
- 7ed5bc5c - Modify entry in CHANGELOG
-
41eedd45...f981da44 - 22 commits from branch
@DouweM I needed to resolve conflicts again and I see that my latest commit disabled the 'automatic merge', that was waiting for build to finish. Can you merge it manually? All is 'green' right now :)
@tmaczukin We still have:
This merge request contains merge conflicts
Added 175 commits:
-
7ed5bc5c...2f2aada3 - 173 commits from branch
master
- 768721dc - Merge branch 'master' into ci/api-triggers
- 96aeaeaf - Update CHANGELOG
-
7ed5bc5c...2f2aada3 - 173 commits from branch
@ayufan Builds MR was merged first - that generated new conflicts. Resolved. I've also removed duplicate from CHANGELOG (variables features for API was entered two times).
Ready to merge - again :)
mentioned in commit 948bb655
mentioned in commit c7ee7eea
mentioned in issue #4218 (closed)
mentioned in issue #10852 (closed)
mentioned in issue #10421 (moved)
Mentioned in commit maxraab/gitlab-ce@c7ee7eea