Thank you for contributing to Script Seed! Here are some notes to help you out.
- If you're making improvements to an existing script, try to keep your commits concise, and explain the reason for the change in a well written commit message.
- If you're adding a new language, make sure your script is executable and
includes a proper shebang line at the top. Prefer
#!/usr/bin/envwhere appropriate.- To pass our simple test harness, your script should print usage instructions
when
-his passed. - Have fun with the message, but make sure it includes the string
You planted awhen run with no args. - Adding a new language requires the following. If you're unsure about any of
these steps, feel free to open a pull request with just the script itself
and we'll help you with the rest.
- Add the seed script to
seeds/. - Add an option to the dropdown in
index.html. - If necessary, install support for the language in the
Dockerfileto allow for testing.
- Add the seed script to
- To pass our simple test harness, your script should print usage instructions
when