feat: Add new config option allow_security_updates_on_concurrent_limit #28
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
truls1502
force-pushed
the
feat/security-bypass-concurrent
branch
2 times, most recently
from
2dcdd27
to
96996d5
Compare
eiriksm
requested changes
Jun 29, 2024
truls1502
changed the title
truls1502
force-pushed
the
feat/security-bypass-concurrent
branch
2 times, most recently
from
8d5fe2a
to
dd534c8
Compare
eiriksm
requested changes
Jun 30, 2024
truls1502
force-pushed
the
feat/security-bypass-concurrent
branch
from
dd534c8
to
18a011b
Compare
|
Awesome thanks 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
We want to get security packages passed on
number_of_concurrent_updatesby default. But for those who want to save CI minutes or not doing it can feel free disable theskip_security_updates_on_concurrent_limit