chore: stop gitignoring scripts/ so seeded problems are shareable + add .env.example - #17
Open
alexandramartinez wants to merge 1 commit into
Conversation
Stop gitignoring the scripts/ folder so seed scripts are version- controlled and shipped with the repo. This gives contributors direct access to the seeded problems, so they can add more test cases to the existing problems and/or create new problems modeled on them. Also add the .env.example template that the README already tells contributors to copy (cp .env.example .env.local), and add a !.env.example negation so it survives the .env* ignore rule. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@alexandramartinez is attempting to deploy a commit to the bighnesh's projects Team on Vercel. A member of the Team first needs to authorize 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
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.
What
Two small repo-hygiene changes:
/scripts. The.gitignorehad a bare/scriptsrule (under the# productionsection, next to/build) that hid the entire seed-script folder from git — so nothing inscripts/was ever version-controlled..env.example. The README already tells contributors tocp .env.example .env.local, but the file didn't exist. Added it, plus a!.env.examplenegation so it survives the.env*ignore rule.Why
The
scripts/folder is where the DataWeave problems get seeded into MongoDB. With it gitignored, contributors cloning the repo had no access to the seeded problem set — the README even documentsscripts/as "Seed scripts" in the project structure, so ignoring it was almost certainly unintentional.By tracking
scripts/, contributors can:all through normal PRs against version-controlled seed data instead of one-off writes to a database.
The
.env.examplecloses a gap in the documented setup flow so a fresh clone can get running without guessing which env vars are needed.Notes
scripts/is empty in this PR (no seed script committed here) — this change only unblocks the folder so seed scripts can be added and shared in follow-ups.🤖 Generated with Claude Code