This repository has been archived by the owner on Dec 3, 2024. It is now read-only.
Resolve .bat File Conflict by Using Unique Hash in Filename on Windows #19
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.
Resolve .bat File Conflict by Using Unique Hash in Filename on Windows
This commit fixes the conflict encountered during the build process on Windows systems. The error was caused by multiple actions attempting to write to the same .bat file.
The solution implemented avoids this conflict by introducing a unique hash into the filename of the .bat file for each action. This ensures that each action writes to a unique file, allowing actions to be executed concurrently without any conflicting writes to the same file, and enabling a smooth build process.
The change includes:
_copy_action_windows
function.For further information, please consult this issue.