Document initial AppSec dogfooding and feature request page
Why is this change being made?
There's no visibility into what AppSec product features the team needs. This MR documents a label the team can use to signify, track, and share those requests.
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Update file appsec-dogfooding-feature-requests.md
Merge request reports
Activity
added HandbookContent label
assigned to @jritchey
added teamApplication Security label
handbook-codequality.json not present... using markdownlint-cli2-codequality.json only
️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes you'll find the code quality report above which can link you to where the error is in your code. Additionally below you'll find a table of the errors. The table has links to the markdown lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error Help MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 7 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 10 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 15 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 16 Multiple consecutive blank lines [Expected: 1; Actual: 3] ️If you need more help please reach out on Slack in #mr-buddies or #handbook.
added 1 commit
- 4e7b2c09 - Update file appsec-dogfooding-feature-requests.md
handbook-codequality.json not present... using markdownlint-cli2-codequality.json only
️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes you'll find the code quality report above which can link you to where the error is in your code. Additionally below you'll find a table of the errors. The table has links to the markdown lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error Help MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 7 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 10 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 13 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 16 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 17 Multiple consecutive blank lines [Expected: 1; Actual: 3] ️If you need more help please reach out on Slack in #mr-buddies or #handbook.
added 1 commit
- 80214a53 - Update file appsec-dogfooding-feature-requests.md
handbook-codequality.json not present... using markdownlint-cli2-codequality.json only
️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes you'll find the code quality report above which can link you to where the error is in your code. Additionally below you'll find a table of the errors. The table has links to the markdown lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error Help MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 11 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 14 Multiple consecutive blank lines [Expected: 1; Actual: 2] ️MD012 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 15 Multiple consecutive blank lines [Expected: 1; Actual: 3] ️If you need more help please reach out on Slack in #mr-buddies or #handbook.
added 1 commit
- 32fa4f3e - Update file appsec-dogfooding-feature-requests.md
added 1 commit
- 2be89ebd - Update file appsec-dogfooding-feature-requests.md
added 1 commit
- d757d341 - Update file appsec-dogfooding-feature-requests.md
handbook-codequality.json not present... using markdownlint-cli2-codequality.json only
️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes you'll find the code quality report above which can link you to where the error is in your code. Additionally below you'll find a table of the errors. The table has links to the markdown lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error Help MD009 content/handbook/security/product-security/application-security/appsec-dogfooding-feature-requests.md 11 Trailing spaces [Expected: 0 or 2; Actual: 1] ️ You have a Trailing spaces error. The practical handbook edits handbook provides more tips, for example removing trailing whitespaces.If you need more help please reach out on Slack in #mr-buddies or #handbook.
added 1 commit
- 9dd091a7 - Update file appsec-dogfooding-feature-requests.md
added 1 commit
- ab545874 - Update file appsec-dogfooding-feature-requests.md
added 1 commit
- bc869e20 - Update file appsec-dogfooding-feature-requests.md
added 1 commit
- 8d7e5352 - Update file appsec-dogfooding-feature-requests.md
requested review from @vdesousa
- Resolved by James Ritchey
- Resolved by Vitor Meireles De Sousa
- Resolved by Vitor Meireles De Sousa
@jritchey just made two small comments, otherwise LGTM
- Resolved by James Ritchey
mentioned in commit 8faf43d1