Skip to content

[Chore]: Move security vulnerabilities workflow out of ci.yaml #4960

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

Closed
jsjoeio opened this issue Mar 7, 2022 · 0 comments · Fixed by #5553
Closed

[Chore]: Move security vulnerabilities workflow out of ci.yaml #4960

jsjoeio opened this issue Mar 7, 2022 · 0 comments · Fixed by #5553
Labels
chore Related to maintenance or clean up security Security related
Milestone

Comments

@jsjoeio
Copy link
Contributor

jsjoeio commented Mar 7, 2022

What is your suggestion?

Move security vulnerabilities workflow out of ci.yaml

Why do you want this feature?

and it can be frustrating to make a doc change or something and have your pr fail because someone found a security issue in some dependency the other day

@code-asher and I were discussing this the other day.

Are there any workarounds to get this functionality today?

Yeah, you have to open a separate PR to fix the vulnerability, merge that then rebase your other PR.

Are you interested in submitting a PR for this?

Happy to do this

@jsjoeio jsjoeio added enhancement Some improvement that isn't a feature chore Related to maintenance or clean up security Security related and removed enhancement Some improvement that isn't a feature labels Mar 7, 2022
@jsjoeio jsjoeio added this to the On Deck - High Priority milestone Mar 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Related to maintenance or clean up security Security related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant