Add SSH content to the Use Git section
What does this MR do and why?
This MR updates the SSH key information in the Install Git page.
Comment from Suzanne:
I wonder if this might also go under Git? Hmmm. It's required, but it's not really about learning Git. Just putting here for consideration. Use SSH keys to communicate with GitLab.
Related issues
- Issue: #499459 (closed)
- Child item: #499465 (closed)
- MR to update navigation: Draft: Add SSH page to Use Git navigation (gitlab-docs!5151 - closed)
Merge request reports
Activity
changed milestone to %17.6
added Technical Writing documentation maintenancerefactor typemaintenance labels
assigned to @brendan777
added 7 commits
- b303ff2e - Create new SSH key page for Use Git section
- 237a3108 - Add introduction for new page
- 7fd2c4d0 - Add prerequisites, supported key types, and checking for existing keys
- 9225cc4d - Add info on how to generate a new ssh key pair
- aa502c7b - Process steps for adding SSH key pair to GitLab
- 08d62ca9 - Fix reference link
- 869e1c6e - Add top-level heading
Toggle commit listadded docs-only label
added 1 commit
- d4db4579 - Add troubleshooting and related topics sections
requested review from @fneill
mentioned in merge request gitlab-docs!5151 (closed)
mentioned in merge request !170261 (merged)
added devopsgovern groupauthentication labels
added sectionsec label
added workflowready for review label and removed sectionsec label
added sectionsec label
- Resolved by Fiona Neill
@fneill, after our call, I will use this MR to update the Install Git page with a line or two that links to the current Generate an SSH key pair section.
Reasons not to have a separate SSH key page under Use Git:
- It duplicates a lot of content already available.
- It does not involve or contain Git commands.
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/topics/git/how_to_install_git/index.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.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
started a merge train
mentioned in commit 0c70d074
added workflowstaging-canary label and removed workflowready for review label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added Category:System Access label