GitHub import: improve documentation
What does this MR do and why?
Implementation for GitHub import: improve documentation (#392754 - closed)
Improves documentation based on the comment here
GitHub import-related documentation has some parts that are not relevant anymore and where not removed on time of code changes.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
changed milestone to %15.11
added Category:Importers Importer:GitHub SoftServeImport documentation typemaintenance workflowin dev + 1 deleted label
added devopsfoundations sectiondev labels
Hey @krisberry-ext!
Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.
Did you know about our community forks? Working from there will make your contribution process easier. Please check it out!
When you're ready for a first review, post
@gitlab-bot ready
. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with@gitlab-bot ready @user1 @user2
.At any time, if you need help, feel free to post
@gitlab-bot help
or initiate a mentor session on Discord. Read more on how to get help.You can comment
@gitlab-bot label <label1> <label2>
to add labels to your MR. Please see the list of allowed labels in thelabel
command documentation.This message was generated automatically. You're welcome to improve it.
added Community contribution label
removed Community contribution label
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/user/project/import/github.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-
added docs-only label
added maintenancerefactor label
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
- Resolved by George Koltsov
Hey @eread, don't you mind reviewing this MR?
requested review from @eread
added workflowin review label and removed workflowin dev label
- Resolved by Kristina Doskich
added Technical Writing docsimprovement labels
removed review request for @eread
requested review from @georgekoltsov
enabled an automatic merge when the pipeline for 577765ff succeeds
mentioned in commit a50ab538
added workflowstaging-canary label and removed workflowin 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 workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added groupimport and integrate label and removed 1 deleted label