-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve ops UX through job/resources renamings #228
Comments
With current COA usage, I'm not sure this is our priority. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The current naming for jobs is sometimes not explicit. E.g. #11 for tf or #218 with a new "hard-reset"
This impacts user experience for service operators, especially as concourse does not support adding documentation to jobs.
Describe the solution you'd like
A consistent naming for jobs/tasks/resources, which makes sense from user perspective.
The text was updated successfully, but these errors were encountered: