Repository navigation
chore: add kiritan-thumbnail assets and cover them in ASSETS_LICENSE.md - #46
Merged
Merged
Conversation
Adds assets/kiritan-thumbnail.png/.gal and lists them in ASSETS_LICENSE.md's Covered Files section alongside the existing kiritan/kiritan-logo assets. The license's scope statement already covers every image under assets/ generically; this keeps the explicit file list in sync with it.
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
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.
Summary
assets/kiritan-thumbnail.png/.gal(a new image asset).ASSETS_LICENSE.md's "Covered Files" section, alongside the existingkiritan/kiritan-logoassets. The license's top-level scope statement already covers every image underassets/generically ("the image files (.png/.gal) underassets/"), so this keeps the explicit file enumeration in sync with that rather than changing any actual terms.assets/aren't covered by WTFPL" note — they're all worded generically (no per-file enumeration), so none needed updating.Test plan
npm run ci(prettier + eslint)fix-unnatural-line-breakslint onASSETS_LICENSE.md