Documentation revision: PAT notification emails
What does this MR do?
Enhances the documentation for the addition of instance-wide personal access token expiry in 12.6. !17344 (merged) added documentation about the admin setting, but it seems useful to document that this feature exists within the PAT documentation.
Adds documentation about the notification emails added by !19296 (merged).
And also mentions impersonation tokens.
Related issues
Author's checklist (required)
-
Follow the Documentation Guidelines and Style Guide. -
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.
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
changed milestone to %13.0
assigned to @bprescott_ and unassigned @mjang1
mentioned in issue #216103 (closed)
assigned to @mjang1 and unassigned @bprescott_
-
@bprescott_ I appreciate the MR. It includes missing links to other PAT docs, and that's helpful. I have a couple of comments that I wasn't sure of -- they might require further review.
assigned to @bprescott_ and unassigned @mjang1
added 1 commit
- 226b1b4d - Apply suggestion to doc/user/profile/personal_access_tokens.md
added 86 commits
-
226b1b4d...05ef70b8 - 84 commits from branch
master - a149f190 - Document PAT notification emails
- 7647169d - Mention impersonation tokens alongside PATs
-
226b1b4d...05ef70b8 - 84 commits from branch
assigned to @mjang1 and unassigned @bprescott_
mentioned in issue #216482
mentioned in commit 166ec19f
added workflowstaging label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
mentioned in issue gitlab-com/support/support-team-meta#2340 (closed)
mentioned in merge request !51436 (merged)
mentioned in merge request !51592 (closed)
added typemaintenance label
