Skip to content

Update Releases API to include issue and MR links

What does this MR do and why?

Describe in detail what your merge request does and why.

This MR exposes the relevant issue and merge request URLs in the Releases API entity, creating parity between the REST and GraphQL APIs. It also updates the documentation to include these changes. Resolves issue #386847 (closed).

I have not added or updated any tests, and I'm out of CI minutes so I'll wait for the MR pipeline to run and see if there's any problems there.

Edit: Per (x) I've requested a reset on my CI minutes.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After
image image
image image

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Create a Release with a tag that has issues & merge requests.
  2. Make an HTTP GET request to http://gdk.test:3000/api/v4/projects/2/releases with appropriate credentials.
  3. Verify that the new links appear under the _links node.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #386847 (closed)

Edited by Nicholas Fason

Merge request reports

Loading