Change shared runner to instance runner
What does this MR do?
Updates usage of 'shared runner' to 'instance runner', as per this decision.
Related issues
- Replace UI usages of shared runner with instanc... (!143480 - merged)
- Update shared runner to instance runner (gitlab-runner#37340 - closed)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
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 likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure 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.
Merge request reports
Activity
assigned to @fneill
added sectionci label
added docs-only label
3 Warnings a177a9fc: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. 1f1c99bf: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. There were no new or modified feature flag YAML files detected in this MR. If the changes here are already controlled under an existing feature flag, please add
the feature flagexists. Otherwise, if you think the changes here don't need
to be under a feature flag, please add the label feature flagskipped, and
add a short comment about why we skipped the feature flag.For guidance on when to use a feature flag, please see the documentation.
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/administration/pages/index.md
(Link to current live version) -
doc/administration/pages/source.md
(Link to current live version) -
doc/administration/settings/continuous_integration.md
(Link to current live version) -
doc/administration/cicd.md
(Link to current live version) -
doc/api/runners.md
(Link to current live version) -
doc/ci/caching/index.md
(Link to current live version) -
doc/ci/cloud_services/index.md
(Link to current live version) -
doc/ci/docker/using_docker_build.md
(Link to current live version) -
doc/ci/docker/using_docker_images.md
(Link to current live version) -
doc/ci/docker/using_kaniko.md
(Link to current live version) -
doc/ci/examples/php.md
(Link to current live version) -
doc/ci/interactive_web_terminal/index.md
(Link to current live version) -
doc/ci/migration/examples/jenkins-maven.md
(Link to current live version) -
doc/ci/migration/circleci.md
(Link to current live version) -
doc/ci/migration/github_actions.md
(Link to current live version) -
doc/ci/migration/jenkins.md
(Link to current live version) -
doc/ci/pipelines/cicd_minutes.md
(Link to current live version) -
doc/ci/quick_start/index.md
(Link to current live version) -
doc/ci/runners/configure_runners.md
(Link to current live version) -
doc/ci/runners/new_creation_workflow.md
(Link to current live version) -
doc/ci/runners/runners_scope.md
(Link to current live version) -
doc/ci/services/mysql.md
(Link to current live version) -
doc/ci/services/postgres.md
(Link to current live version) -
doc/ci/services/redis.md
(Link to current live version) -
doc/ci/testing/code_quality.md
(Link to current live version) -
doc/subscriptions/gitlab_com/index.md
(Link to current live version) -
doc/subscriptions/bronze_starter.md
(Link to current live version) -
doc/topics/autodevops/requirements.md
(Link to current live version) -
doc/tutorials/automate_runner_creation/index.md
(Link to current live version) -
doc/user/application_security/container_scanning/index.md
(Link to current live version) -
doc/user/application_security/dast/browser/configuration/variables.md
(Link to current live version) -
doc/user/gitlab_com/index.md
(Link to current live version) -
doc/user/group/access_and_permissions.md
(Link to current live version) -
doc/user/packages/container_registry/index.md
(Link to current live version) -
doc/user/packages/yarn_repository/index.md
(Link to current live version) -
doc/user/project/clusters/cluster_access.md
(Link to current live version) -
doc/user/project/pages/introduction.md
(Link to current live version) -
doc/user/project/repository/forking_workflow.md
(Link to current live version) -
doc/user/project/settings/import_export_troubleshooting.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Category Reviewer Maintainer backend @jwanjohi
(UTC+3, 3 hours ahead of author)
@bmarjanovic
(UTC+1, 1 hour ahead of author)
frontend @mcavoj
(UTC+1, 1 hour ahead of author)
@mrincon
(UTC+1, 1 hour ahead of author)
Please check reviewer's status!
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by Ghost User-
- Resolved by Fiona Neill
- Resolved by Fiona Neill
- Resolved by Fiona Neill
- Resolved by Fiona Neill
- Resolved by Fiona Neill
- Resolved by Fiona Neill
- Resolved by Fiona Neill
- Resolved by Fiona Neill