Skip to content

Start renaming CI/CD minutes to compute credits

Marcel Amirault requested to merge docs-update-compute-credits into master

What does this MR do?

As per the related issues, the CI/CD minutes that you can purchase are renamed to compute credits, so we need to update the docs and UI to match.

This has already been changed in the user-facing marketing pages:

So I think we really need to get this updated ASAP.

All instances of these terms need to be updated to compute credits:

  • CI/CD minutes
  • CI minutes
  • pipeline minutes
  • CI pipeline minutes
  • minutes (when the context is about CI/CD minutes / compute credits)

This MR updates all UI text, docs, and specs to match the terminology we are now marketing to our users. It's a big one, but unfortunately I think it's the best solution to make sure nothing is missed and everything stays in sync. All the tests pass, and I verified as much as I could in the UI, you can see the before/after changes in the screenshots below.

Related issues

Screenshots

Instance settings:

  • Before:
    Screenshot_2023-04-07_at_17.50.00
  • After:
    Screenshot_2023-04-07_at_17.49.21

Admin settings for one group:

  • Before:
    Screenshot_2023-04-07_at_18.41.35
  • After:
    Screenshot_2023-04-07_at_18.43.09

Group usage page:

  • Before:
    Screenshot_2023-04-07_at_18.45.28
  • After:
    Screenshot_2023-04-07_at_18.45.56

Namespace usage page:

  • Before:
    Screenshot_2023-04-07_at_18.44.53
  • After:
    Screenshot_2023-04-07_at_18.44.38

** Buy Minutes page (/-/subscriptions/buy_minutes?selected_group=GROUP_ID) **

Before After
buy_minutes_before buy_minutes_after

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by Ian Pedowitz

Merge request reports

Loading