Use active voice in pipeline error copy
The following discussion from !57838 (merged) should be addressed:
-
@mkaeppler
started a discussion: (+10 comments)@fabiopitino
I'm a bit fuzzy on how our site translation system works since I don't usually work on product-y aspects of GitLab; it looks though as if these are rendered straight into view templates and API entities without going through gettext first. Is this good enough?
We should consider:
- resolving these strings through gettext, since currently they are untranslated
- changing the copy to use active not passive voice