This repository has been archived by the owner on Aug 25, 2023. It is now read-only.
Insert datasec pre-commit #25
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![meli-datasec-pii-validation[bot]](https://avatars.githubusercontent.com/u/245516?s=60&v=4){kind=small}
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the pre-commit configurations to use DataSec hook (Aegis), following on from what was previously
communicated in workplace.
It is generated automatically and therefore its revision is requested.
The following behavior is expected:
.pre-commit-config.yaml.WebSec hook (SAST)
and DataSec hook (Aegis) hooks are added.
.pre-commit-config.yamlonly DataSec hook is added.Important
Both SAST and Aegis hooks are required.
Contact
If you have any questions contact [email protected]
or slack.