People who have improved Shipley Farms’ public tools. Newest first.
This file exists so a contribution here is citable. A merged pull request on GitHub is public and permanent, and your name below is a plain record that we accepted it. If you are a student and someone asks us to confirm you contributed, we will.
We are not going to inflate anyone’s work. A typo fix is listed as a typo fix and a shipping integration is listed as a shipping integration. That honesty is what makes the list worth being on.
| Contributor | Contribution | Merged |
|---|---|---|
| @Kira-Saints | Typo fix on /helloworld (#16) |
2026-10-18 |
| @tadaokatzuki | Typo fix on /helloworld (#13) |
2026-10-15 |
| @O1sumitkumar | Typo fix on /helloworld (#10) |
2026-10-06 |
| @aipd506 | Typo fix on /helloworld (#8) |
2026-10-02 |
| @Jah-yee | Typo fix on /helloworld (#6) |
2026-09-30 |
| You could be here. See CONTRIBUTING.md. |
/helloworld always carries exactly one deliberate misspelling. Fix it and you go in the chain in
site/SEEDED.md, which records who found which one, in order. It is the same
honesty rule as the table above: the chain says you fixed a typo, because you fixed a typo. What
makes it worth being in is that it is a real list of real people who each changed a live page.
Have a pull request merged. That is the whole requirement. There is no minimum size, and the first task on https://shipleyfarmsbeef.com/helloworld?utm_source=github&utm_medium=repo&utm_campaign=shipley-integrations&utm_content=contributors counts.
Maintainers: add a row at the TOP of the table when you merge, in the same commit as the merge where practical. The table is newest first, so a row appended at the bottom contradicts the line under the heading. Use the contributor’s preferred name and link their GitHub profile if they want it linked. Ask first rather than assuming; some people contribute under a name they do not want indexed.
We will: confirm that you contributed, describe what you built, and say whether we use it. If you need that in writing for a course or an application, ask.
We will not: write you a personal reference on the strength of a pull request alone, or describe a contribution as larger than it was. If you work with us long enough that a real reference makes sense, that is a different conversation and a welcome one.