fix(stylelint): prettify and ignore markdownlint extension

Author: wewoor

.gitlab/README.md

@@ -6,16 +6,16 @@ There are some useful `MR, Issue, Test Plan` description templates collected fro
 
 It's used when create new `issue`, now we only provide 4:
 
-- [Bug.md](./issue_template/Bug.md)
-- [Feature.md](./issue_template/Feature.md)
-- [Refactoring.md](./issue_template/Refactoring.md)
-- [Test.md](./issue_template/Test.md)
+-   [Bug.md](./issue_template/Bug.md)
+-   [Feature.md](./issue_template/Feature.md)
+-   [Refactoring.md](./issue_template/Refactoring.md)
+-   [Test.md](./issue_template/Test.md)
 
 ## MR Template
 
 It's used when create new `Merge Request`.
 
-- [Document.md](./issue_template/Document.md)
+-   [Document.md](./issue_template/Document.md)
 
 ## More
 

.gitlab/issue_templates/Test.md

@@ -39,7 +39,7 @@ test plan](https://testing.googleblog.com/2011/09/10-minute-test-plan.html) and
 model](https://code.google.com/archive/p/test-analytics/wikis/AccExplained.wiki). -->
 
 |            | Secure | Responsive | Intuitive | Reliable |
-|------------|:------:|:----------:|:---------:|:--------:|
+| ---------- | :----: | :--------: | :-------: | :------: |
 | Admin      |        |            |           |          |
 | Groups     |        |            |           |          |
 | Project    |        |            |           |          |

.gitlab/merge_request_templates/Document.md

@@ -19,51 +19,51 @@ Link related issues below. Insert the issue link or reference after the word "Cl
 
 ## Author's checklist (required)
 
-- [ ] Follow the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).
-- If you have **Developer** permissions or higher:
-  - [ ] Ensure that the [product tier badge](https://docs.gitlab.com/ee/development/documentation/styleguide.html#product-badges) is added to doc's `h1`.
-  - [ ] Apply the ~documentation label, plus:
-    - The corresponding DevOps stage and group labels, if applicable.
-    - ~"development guidelines" when changing docs under `doc/development/*`, `CONTRIBUTING.md`, or `README.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](https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments).
+-   [ ] Follow the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).
+-   If you have **Developer** permissions or higher:
+    -   [ ] Ensure that the [product tier badge](https://docs.gitlab.com/ee/development/documentation/styleguide.html#product-badges) is added to doc's `h1`.
+    -   [ ] Apply the ~documentation label, plus:
+        -   The corresponding DevOps stage and group labels, if applicable.
+        -   ~"development guidelines" when changing docs under `doc/development/*`, `CONTRIBUTING.md`, or `README.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](https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments).
 
 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](https://docs.gitlab.com/ee/user/permissions.html).
-- [ ] Link docs to and from the higher-level index page, plus other related docs where helpful.
-- [ ] Add the [product tier badge](https://docs.gitlab.com/ee/development/documentation/styleguide.html#product-badges) accordingly.
-- [ ] Add [GitLab's version history note(s)](https://docs.gitlab.com/ee/development/documentation/styleguide.html#text-for-documentation-requiring-version-text).
-- [ ] Add/update the [feature flag section](https://docs.gitlab.com/ee/development/documentation/feature_flags.html).
+-   [ ] Update the [permissions table](https://docs.gitlab.com/ee/user/permissions.html).
+-   [ ] Link docs to and from the higher-level index page, plus other related docs where helpful.
+-   [ ] Add the [product tier badge](https://docs.gitlab.com/ee/development/documentation/styleguide.html#product-badges) accordingly.
+-   [ ] Add [GitLab's version history note(s)](https://docs.gitlab.com/ee/development/documentation/styleguide.html#text-for-documentation-requiring-version-text).
+-   [ ] Add/update the [feature flag section](https://docs.gitlab.com/ee/development/documentation/feature_flags.html).
 
 ## Review checklist
 
 All reviewers can help ensure accuracy, clarity, completeness, and adherence to the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).
 
-**1. Primary Reviewer**
+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.
+-   [ ] 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**
 
-- [ ] 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](https://about.gitlab.com/handbook/product/product-categories/#devops-stages).
-  - [ ] Ensure docs metadata are present and up-to-date.
-  - [ ] Ensure ~"Technical Writing" and ~"documentation" are added.
-  - [ ] Add the corresponding `docs::` [scoped label](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=docs%3A%3A).
-  - [ ] If working on UI text, add the corresponding `UI Text` [scoped label](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=ui+text).
-  - [ ] Add ~"tw::doing" when starting work on the MR.
-  - [ ] Add ~"tw::finished" if Technical Writing team work on the MR is complete but it remains open.
+-   [ ] 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](https://about.gitlab.com/handbook/product/product-categories/#devops-stages).
+    -   [ ] Ensure docs metadata are present and up-to-date.
+    -   [ ] Ensure ~"Technical Writing" and ~"documentation" are added.
+    -   [ ] Add the corresponding `docs::` [scoped label](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=docs%3A%3A).
+    -   [ ] If working on UI text, add the corresponding `UI Text` [scoped label](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=ui+text).
+    -   [ ] Add ~"tw::doing" when starting work on the MR.
+    -   [ ] Add ~"tw::finished" if Technical Writing team work on the MR is complete but it remains open.
 
 For more information about labels, see [Technical Writing workflows - Labels](https://about.gitlab.com/handbook/engineering/ux/technical-writing/workflow/#labels).
 
 For suggestions that you are confident don't need to be reviewed, change them locally
 and push a commit directly to save others from unneeded reviews. For example:
 
-- Clear typos, like `this is a typpo`.
-- Minor issues, like single quotes instead of double quotes, Oxford commas, and periods.
+-   Clear typos, like `this is a typpo`.
+-   Minor issues, like single quotes instead of double quotes, Oxford commas, and periods.
 
 For more information, see our documentation on [Merging a merge request](https://docs.gitlab.com/ee/development/code_review.html#merging-a-merge-request).
 

.vscode/settings.json

@@ -6,5 +6,6 @@
         "source.fixAll.eslint": true,
         "source.fixAll.markdownlint": false,
         "source.fixAll.stylelint": true
-    }
+    },
+    "markdownlint.ignore": ["**/*.md"]
 }