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.
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.
If it's all the same to you, I'd rather this schedule was more gentile. Porch doesn't have a CD process, so there would be far more churn than releases and deployments. I'd suggest weekly or monthly would be quite enough to ward off evil.
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.
Then I'd suggest acting on them weekly or monthly, but leaving the daily schedule so that if a "critical" pops up it can dealt with. The actual frequency of PRs is much less than daily (typically 2-3 per month), so best case is you see the 3 PRs at the end of the month, worst case is you sit on a critical CVE for that same time.
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.
Very well. Thanks for enabling it in any event. Been collecting dust in my to-do for years.