From 48539e1e02d7b13f3d0d6830da9277d39cae37d9 Mon Sep 17 00:00:00 2001 From: Amy Qualls Date: Mon, 18 Sep 2023 18:42:54 +0000 Subject: [PATCH] chore: Update which docs files are linted --- .gitlab-ci.yml | 4 ++-- SECURITY.md | 15 ++++++++------- 2 files changed, 10 insertions(+), 9 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index c44d7de8..172c2800 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -67,9 +67,9 @@ check_docs_markdown: extends: .documentation script: # Lint prose - - vale --minAlertLevel error docs README.md + - vale --minAlertLevel error docs *.md # Lint Markdown - - markdownlint --config .markdownlint.yml 'docs/**/*.md' README.md + - markdownlint --config .markdownlint.yml 'docs/**/*.md' *.md lint_commit: stage: test diff --git a/SECURITY.md b/SECURITY.md index bdd5e170..bf176187 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -16,13 +16,15 @@ Consider adding the `/confidential` quick action to a project issue template. - Add any additional labels you know apply. Additional labels will be applied by the security team and other engineering personnel, but it will help with the triage process: - - [`~"type::bug"`, `~"type::maintenance"`, or `~"type::feature"` if appropriate](https://about.gitlab.com/handbook/engineering/security/security-engineering-and-research/application-security/vulnerability-management.html#vulnerability-vs-feature-vs-bug) - - Team or devops lifecycle labels - - `~customer` if issue is a result of a customer report - - `~internal customer` should be added by team members when the issue + + - [`~"type::bug"`, `~"type::maintenance"`, or `~"type::feature"` if appropriate](https://about.gitlab.com/handbook/engineering/security/security-engineering-and-research/application-security/vulnerability-management.html#vulnerability-vs-feature-vs-bug) + - Team or DevOps lifecycle labels + - `~customer` if issue is a result of a customer report + - `~internal customer` should be added by team members when the issue impacts GitLab operations. - - `~dependency update` if issue is related to updating to newer versions of the dependencies GitLab requires. - - `~featureflag::` scoped labels if issue is for a functionality behind a feature flag + - `~dependency update` if issue is related to updating to newer versions of the dependencies GitLab requires. + - `~featureflag::` scoped labels if issue is for a functionality behind a feature flag + - Issues that contain customer specific data, such as private repository contents, should be assigned `~keep confidential`. If possible avoid this by linking resources only available to GitLab team member, for example, the originating @@ -35,4 +37,3 @@ general discussion and examples appropriate for public disclosure prior to release. For review by the Application Security team, @ mention `@gitlab-com/gl-security/appsec`. -