-
Notifications
You must be signed in to change notification settings - Fork 10
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
chore(tools): enable Trunk & Semgrep #11
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some questions about semgrep. I'm also worried about including Trunk because it has been so flakey and I don't really expect JS devs to be using it (yet? at all?)
Thinking about this more, I think we should ensure that Trunk is just additive/optional. I believe this PR does just that, correct? |
Co-authored-by: blaine-arcjet <[email protected]>
Trunk doesn't do anything by itself - it runs all the linters so we don't need to set them up individually. You should be running it automatically locally before pushing so this is just to catch anything in CI that was missed (or not run). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. We can adjust anything that is needed as we go.
No description provided.