First of all, welcome, brave soul. If you're reading this, either:
- You've found a bug (congrats, the prophecy foretold this),
- You're bored at work and this repo seemed quirky,
- Or you just love pain — which makes you one of us.
Please ensure:
- You're using your brain and not just autopilot copypasta mode.
- You've read the code (or at least pretended to — we respect commitment to the bit).
- You're not about to rewrite everything in [insert trendy language here] because "it's cleaner, bro".
- Fork this chaos.
- Clone your fork like a true hacker in a 90s movie.
- Create a new branch (please don't call it
fix-stufforpatch-1, have some flair). - Write code. Break stuff. Fix it. Repeat until enlightened.
- Commit with a message that tells us something (no "Update README" ten times, we beg you).
- PR like a Rockstar. Open a Pull Request. Add a description that's more helpful than “fixed stuff”.
- Follow the existing code style — we use ESLint and Prettier to keep the entropy symmetrical.
- Write meaningful commit messages. Not poetic, not cryptic, just... coherent.
- If you’re introducing bugs cleverly disguised as features, at least add a test. Predictable failure is still a kind of success, philosophically speaking.
- Found a bug? Open an issue.
- Got a feature idea? Open an issue.
- Spiraling after realizing your entire app is just an API wrapper? Go outside, touch grass, then open an issue.
If your contribution doesn’t break everything — amazing. If it has tests — we will literally throw a virtual party in your honor.
We may:
- Approve your PR.
- Roast your code (lovingly).
- Ghost you (not ideal, but hey, we’re developers).
This repo is a digital organism — sometimes alive, sometimes undead. By contributing, you agree to:
- Embrace the absurdity,
- Accept constructive chaos,
- And debug like the universe is watching (because it is).
Thanks for contributing! Or at least reading this far — that’s contribution enough in spirit.