feat: workspace-concurrency based on cores amount #3574
Merged
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
PabloSzx
force-pushed
the
core-amount-workspace-concurrency
branch
from
be97234 to
0f9efcb
Compare
zkochan
requested changes
Jul 2, 2021
PabloSzx
force-pushed
the
core-amount-workspace-concurrency
branch
from
0f9efcb to
ee15acf
Compare
zkochan
force-pushed
the
core-amount-workspace-concurrency
branch
from
ee15acf to
16dc9ee
Compare
zkochan
approved these changes
Jul 5, 2021
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.
I frecuently encounter the situation that in GitHub actions I have to override workspace-concurrency for the workflow to not overload, but in my computer I have many more cores to work faster, and it was not possible to set the concurrency limit based on the cores of the host