Skip to content

Commit

Permalink
Update MegaLinter to Version 7 + CoD + Security (#69)
Browse files Browse the repository at this point in the history
* Update mega-linter.yml to Version 7

* Update CODE_OF_CONDUCT.md

* Update SECURITY.md

---------

Co-authored-by: ptahmose <[email protected]>
  • Loading branch information
FelixS90 and ptahmose authored Oct 19, 2023
1 parent 470bae2 commit 3581f6b
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/mega-linter.yml
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ jobs:
id: ml
# You can override MegaLinter flavor used to have faster performances
# More info at https://megalinter.io/flavors/
uses: oxsecurity/megalinter/flavors/dotnet@v6
uses: oxsecurity/megalinter/flavors/dotnet@v7
env:
# All available variables are described in documentation
# https://megalinter.io/configuration/
Expand Down
2 changes: 1 addition & 1 deletion CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Contributor Covenant Code of Conduct

This Code of Conduct complements the [ZEISS Social Media Netiquette](https://www.zeiss.com/corporate/int/legal-information/netiquette.html).
This Code of Conduct complements the [ZEISS Social Media Netiquette](https://www.zeiss.com/corporate/en/legal-information/netiquette.html).

## Our Pledge

Expand Down
4 changes: 2 additions & 2 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Security Policy

Any security issues should be submitted directly to github.microscopy@zeiss.com. In order to determine whether you are dealing with a security issue, ask yourself these two questions:
Any security issues should be submitted directly through [privately reporting a security vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability). In order to determine whether you are dealing with a security issue, ask yourself these two questions:

Can I access something that's not mine, or something I shouldn't have access to?
Can I disable something for other people?

If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, just email us.
If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, just follow the instructions linked above.

0 comments on commit 3581f6b

Please sign in to comment.