Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linter Updates and Markdown Format #28

Merged
merged 3 commits into from
Nov 19, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 23 additions & 23 deletions .devcontainer/devcontainer.json
Original file line number Diff line number Diff line change
@@ -1,25 +1,25 @@
{
"name": "Markdown Editing",
"image": "mcr.microsoft.com/devcontainers/base:bullseye",
// Features to add to the dev container. More info: https://containers.dev/implementors/features.
// "features": {},
// Configure tool-specific properties.
"customizations": {
// Configure properties specific to VS Code.
"vscode": {
// Add the IDs of extensions you want installed when the container is created.
"extensions": [
"yzhang.markdown-all-in-one",
"DavidAnson.vscode-markdownlint",
"shd101wyy.markdown-preview-enhanced",
"bierner.github-markdown-preview"
]
}
}
// Use 'forwardPorts' to make a list of ports inside the container available locally.
// "forwardPorts": [],
// Use 'postCreateCommand' to run commands after the container is created.
// "postCreateCommand": "uname -a",
// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
// "remoteUser": "root"
"name": "Markdown Linting",
"image": "mcr.microsoft.com/devcontainers/javascript-node:16-bullseye",
// Features to add to the dev container. More info: https://containers.dev/implementors/features.
// "features": {},
// Configure tool-specific properties.
"customizations": {
// Configure properties specific to VS Code.
"vscode": {
// Add the IDs of extensions you want installed when the container is created.
"extensions": [
"yzhang.markdown-all-in-one",
"DavidAnson.vscode-markdownlint",
"shd101wyy.markdown-preview-enhanced",
"bierner.github-markdown-preview"
]
}
}
// Use 'forwardPorts' to make a list of ports inside the container available locally.
// "forwardPorts": [],
// Use 'postCreateCommand' to run commands after the container is created.
// "postCreateCommand": "uname -a",
// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
// "remoteUser": "root"
}
2 changes: 1 addition & 1 deletion .github/linters/.markdown-lint.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Default state for all rules
default: true
# MD013/line-length
MD013: false
MD013: false
5 changes: 2 additions & 3 deletions .github/settings.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,13 +17,13 @@ repository:
# role. If there are questions, please contact one of the chairs.
collaborators:
# Chairs and Admin Help
- username:
- username:
permission: admin

# Contributors
# all permissions except admin

- username:
- username:
permission: push

labels:
Expand All @@ -33,6 +33,5 @@ labels:
color: ff8c00
- name: meeting
color: 00ff00

# additional colors in this palette:
# 7f0000 , 1e90ff, ffdab9, ff69b4
18 changes: 18 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
lerna-debug.log*
.pnpm-debug.log*

# Diagnostic reports (https://nodejs.org/api/report.html)
report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json

# Dependency directories
node_modules/
jspm_packages/

# Optional npm cache directory
.npm
13 changes: 7 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,12 +23,13 @@ This SIRT's motivation is to make available the incident response resources to a
To develop a cohort of trustworthy, vendor-neutral, vetted, well-orchestrated and experienced group of security professionals

**_EXPRESSLY OUT OF SCOPE:_**
⊲ Anything involving vulnerabilities in closed-source/proprietary software
⊲ Security improvements to open-source software that are not tactically essential to the
patching of newly-reported, high- and critical-impact vulnerabilities in open-source
software
⊲ Helping projects or individual enterprises with remediating their security exposures
from another open-source project’s security vulnerabilities

- Anything involving vulnerabilities in closed-source/proprietary software
- Security improvements to open-source software that are not tactically essential to the
patching of newly-reported, high- and critical-impact vulnerabilities in open-source
software
- Helping projects or individual enterprises with remediating their security exposures
from another open-source project’s security vulnerabilities

## Prior Work

Expand Down
Loading