gitlab
/
cli
mirror of https://gitlab.com/gitlab-org/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore: Update which docs files are linted

This commit is contained in:
Amy Qualls 2023-09-18 18:42:54 +00:00 committed by Gary Holtz
parent 7aee063751
commit 48539e1e02
2 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.gitlab-ci.yml
View File

@ -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

15
SECURITY.md
View File

@ -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`.