Adds a feature to merge multiple build folders. #1561
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.
Description
When we create an NFT collection, we may repeat the build several times. In doing so, we remove those with poor results and select the good ones.
This function merges the results of several builds.
Usage
First of all, if you have already installed HashLips, do npm install again.
The simplest method is to merge the build results in build_a, build_b, and build_c into the build folder.
NOTE: In this case, the contents of the original build folder will be deleted.
At this time, if there are items with the same DNA, the following message will be displayed and only the first one will be adopted.
If you want to shuffle the order of the results after merging, add the -s option.
Help is also available.
npm run merge -- help
Example
Related issues
#1189