Help build something useful.

All projects under th30d4y are open source. Contributions of any size — bug fixes, documentation, features, feedback — are welcome.

View repositories ↗Open an issue

Step by step

01

Fork the repository

Start by forking the repository to your own GitHub account. This gives you a personal copy to work on without affecting the original.

gh repo fork th30d4y/<repo-name>
02

Clone your fork

Clone your forked repository locally so you can make changes on your machine.

git clone https://github.com/<your-username>/<repo-name>.git
cd <repo-name>
03

Create a branch

Create a new branch for your feature or fix. Use a short, descriptive name.

git checkout -b feat/your-feature-name
# or
git checkout -b fix/short-description
04

Make your changes

Write clean, focused code. Keep changes scoped — one feature or fix per pull request makes review faster.

05

Commit with a clear message

Write a concise commit message describing what changed and why.

git add .
git commit -m "feat: add rate-limit retry logic"
# Types: feat | fix | docs | refactor | test | chore
06

Push and open a pull request

Push your branch and open a pull request against the main branch. Describe what your PR does and reference any related issues.

git push origin feat/your-feature-name

What makes a good contribution

◈

Keep PRs small

One logical change per PR. Smaller PRs are reviewed faster and are easier to merge.

◇

Write meaningful commits

Use conventional commit prefixes: feat, fix, docs, refactor, test, chore.

●

Test your changes

Make sure your changes work before submitting. If the project has tests, run them.

✦

Document what matters

If your change adds new behaviour, update any relevant docs or comments.

⑂

Be respectful

Keep discussions technical and constructive. Everyone is here to learn and build.

↑

Follow existing style

Match the code style, naming conventions, and patterns already in the project.

Be excellent to each other.

This project follows a simple rule: treat everyone with respect. Harassment, personal attacks, and unconstructive criticism have no place here. If you see behaviour that violates this, open an issue or reach out directly.

Start contributing today.

Browse open issues, fork a repository, or suggest an improvement.