Show better errors from GraphQL on Releases
What does this MR do and why?
A generic "Something went wrong..." error makes it hard for users to understand how to fix any issues in the form. Instead, we should utilize the good error messages provided by the various release services.
We also add a clarifying message for when a user attempts to create a release with a protect tag when they are not allowed.
Changelog: added
Screenshots or screen recordings
How to set up and validate locally
- Protect a tag
- Impersonate (or log in as) a user that is unable to create a tag matching the above rule
- attempt to create a release that would create a tag that matches the rule (Deployments > Releases, New Release)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
For #334940 (closed)
Edited by Andrew Fontaine