Return deploy key title when humanizing access levels
What does this MR do and why?
Return deploy key title when humanizing access levels
When we humanize a protected ref access level with a deploy key we used to return "Deploy Key", however, if we look at how users and groups are humanized we return their names which identifies the user or group rather than the role.
As a deploy key is not a role but rather a thing we should return the name so users have more context.
Changelog: changed
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- Create a project deploy key and grant write permissions
- Allow the deploy key to push to a protected branch
- Call the Protected branches API and observe the response
- Allow the deploy key to create protected tags
- Call the Protected tags API and observe the response
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.