Clarify Authenticating to the Container Registry with CI/CD details
What does this MR do?
Related issues
Author's checklist (required)
-
Follow the Documentation Guidelines and Style Guide. - If you have
developer
access or higher (for example, GitLab team members or Core Team members)-
Apply the documentation label, plus: - The corresponding DevOps stage and group label, if applicable.
-
development guidelines when changing docs under
doc/development/*
,CONTRIBUTING.md
, orREADME.md
. -
development guidelines and Documentation guidelines when changing docs under
development/documentation/*
. - development guidelines and Description templates (.gitlab/*) when creating/updating issue and MR description templates.
-
Assign the designated Technical Writer.
-
Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.
When applicable:
-
Update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Add GitLab's version history note(s). -
Add the product tier badge. -
Add/update the feature flag section. -
If you're changing document headings, search doc/*
,app/views/*
, andee/app/views/*
for old headings replacing with the new ones to avoid broken anchors.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage. -
Add Technical Writing and docs::
workflow label. -
Add docs-only when the only files changed are under doc/*
.
-
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Merge request reports
Activity
added documentation label
marked the checklist item Apply the documentation label, plus: as completed
marked the checklist item Follow the Documentation Guidelines and Style Guide. as completed
assigned to @sselhorn
marked the checklist item Assign the designated Technical Writer. as completed
assigned to @marcel.amirault and unassigned @sselhorn
5 Warnings ⚠ 9da78402: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines. ⚠ b73dcebd: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. ⚠ b73dcebd: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines. ⚠ This merge request includes more than 10 commits. Each commit should meet the following criteria: - Have a well-written commit message.
- Has all tests passing when used on its own (e.g. when using git checkout SHA).
- Can be reverted on its own without also requiring the revert of commit that came before it.
- Is small enough that it can be reviewed in isolation in under 30 minutes or so.
If this merge request contains commits that do not meet this criteria and/or contains intermediate work, please rebase these commits into a smaller number of commits or split this merge request into multiple smaller merge requests.
⚠ This merge request does not refer to an existing milestone. 1 Message 📖 This merge request adds or changes files that require a review from the Technical Writing team. Documentation review
The following files require a review from a technical writer:
doc/user/packages/container_registry/index.md
doc/user/profile/personal_access_tokens.md
The review does not need to block merging this merge request. See the:
- Technical Writers assignments for the appropriate technical writer for this review.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
🚫 DangerEdited by 🤖 GitLab Bot 🤖- Resolved by Ben Bodenmiller
- Resolved by Ben Bodenmiller
added Community contribution label
- Resolved by Ben Bodenmiller
@sselhorn Sorry, I only had a chance to look at this now and noticed that it's Package related. Could you suggest an engineer to verify these changes for us?
assigned to @sselhorn
unassigned @sselhorn
assigned to @ggelatti
unassigned @marcel.amirault
- Resolved by Suzanne Selhorn
assigned to @hswimelar
assigned to @bbodenmiller and unassigned @ggelatti
- Resolved by Ben Bodenmiller
mentioned in merge request !28958 (merged)
- Resolved by Ben Bodenmiller
Updated based on !34565 (comment 365597699).
assigned to @sselhorn and unassigned @bbodenmiller
added twdoing label
unassigned @sselhorn
removed twdoing label
unassigned @10io
assigned to @sselhorn and unassigned @jhampton and @hswimelar
- Resolved by Suzanne Selhorn