You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository has exceeded the development grace period, and the repo owner must decide if certain security scan tooling should be activated.
If this repository houses code that touches production in any capacity, code scanning and secret scanning must be enforced. See the SDLC - Secure Coding Guidelines for more details
What do I need to do?
You can activate code scanning and/or secret scanning by creating the labels: activate-code-scanning: true or activate-secret-scanning: true, respectively.
To stop this issue from being recreated, meaning your project does not require these scans, you can conversely create the labels: activate-code-scanning: false and/or activate-secret-scanning: false.
Once you have created the labels to specify your choice, you can close this issue. If you choose to have code scanning activated, a PR will be opened suggesting a Github Action worflow.
If you have issues or questions, please reach out to #internal-security-n-compliance on slack.
The text was updated successfully, but these errors were encountered:
This is an issue generated by github-tools
Description
This repository has exceeded the development grace period, and the repo owner must decide if certain security scan tooling should be activated.
If this repository houses code that touches production in any capacity, code scanning and secret scanning must be enforced. See the SDLC - Secure Coding Guidelines for more details
What do I need to do?
activate-code-scanning: true
oractivate-secret-scanning: true
, respectively.activate-code-scanning: false
and/oractivate-secret-scanning: false
.The text was updated successfully, but these errors were encountered: