Better: Prepend .gitconfig with random hash to allow concurrency #9219
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.
Hello,
I followed the advice here https://github.com/dependabot/dependabot-script/blob/main/update-script.rb#L32 and went with looping all dependencies. I also went a bit further and added https://github.com/grosser/parallel with an each in process to speed up the handling of dependencies.
But I faced the issue that all processes try to update the same .gitconfig file at the same time which is locked.
The fix I propose here is to prepend the .gitconfig file name with a random hash to avoid conflicts