Add new hashes - #38
Open
dnenns wants to merge 1 commit into
Open
Conversation
Author
|
Side Note: I am a bit unsure about if I put the hashes into the appropriate files. I tried gathering information from the discord and just gave it a shot |
dnenns
force-pushed
the
dnenns_add_hashes_1
branch
3 times, most recently
from
August 2, 2026 15:44
18e17f5 to
5fc32fe
Compare
dnenns
force-pushed
the
dnenns_add_hashes_1
branch
from
August 2, 2026 19:23
5fc32fe to
81f91c6
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hashes were calculated using default offset/prime and transforming all strings to lower case