test title
References #4264 (closed)
Merge request reports
Activity
mentioned in issue #4264 (closed)
@ayufan I've added CI data to commits list and commit details. Should we add something else?
mentioned in issue #5599 (closed)
Added 1 commit:
- 69bffa16 - Update ./doc/api
Added 1 commit:
- 13aef532 - Modify commits API CI data, add CI data to merge_request API
Added 1 commit:
- ac5b250f - Fix error in Commit to Ci::Commit delegation
@DouweM @rspeicher Can you review?
Added 1 commit:
- be7a784d - Add some fixes after review
Added 1 commit:
- 66221057 - Modify commits documentation API style [ci skip]
Added 1 commit:
- 648a2797 - Move build data to 'last_build' namespace in commit details
@DouweM I've added
status
and moved all build data tolast_build
namespace.@tmaczukin We thought with @DouweM about the
last_build
,build_
and other nesting possibilities and in the end decided to put that on hold till we decide how it should look like in context of deployments that we plan to introduce in one of the upcoming releases.We already have the
status
exposed, so it's good enough.Added 1 commit:
-
56a45b09 - Modify notes about
duration
unit in commits and merge_requests API documentation [ci skip]
-
56a45b09 - Modify notes about
@ayufan So, to be clear - at the moment we will leave this MR and not merge it into
8.4
release. We will get back here in one of future releases, yes?And also one question - I've moved
status
tolast_build
and now the tests are broken. If we leavelast_build
in the future then should we update tests and leave a notice in documentation OR should we movestatus
back to commit?Added 1 commit:
-
01a40700 - Move
status
field back directly to commit data in API
-
01a40700 - Move
@tmaczukin still planning on finishing this up? :)