Repository navigation
docs: add first-evening template setup guide - #21
Merged
fabianzimber merged 1 commit intoAug 18, 2026
Merged
fabianzimber merged 1 commit into
fabianzimber merged 1 commit into
Conversation
fabianzimber
approved these changes
Aug 18, 2026
fabianzimber
left a comment
Member
There was a problem hiding this comment.
@tasodoufu Thank you alot for the contribution. Looks good and clean 👍
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.
Problem
New users may clone the template repository itself and miss the required placeholder updates before their first publish.
Change
Adds a short README “First evening” section covering:
npm ci && npm test && npm run buildverification;User impact
Template users get a concise first-use checklist without changing runtime behavior.
Verification
npm run lintnpm run typechecknpm run test:cinpm run buildgit diff --checkThe issue was rechecked immediately before push: it is OPEN, unassigned, has no comments indicating active work, and no open PR overlaps
README.md.Closes #17