Skip to content

Latest commit

 

History

History
44 lines (27 loc) · 2.02 KB

File metadata and controls

44 lines (27 loc) · 2.02 KB

Contributing to ResourceChest

First off — thank you for considering a contribution! ResourceChest is community-driven, and every addition, fix, or suggestion makes these collections better for everyone.

Code of Conduct

We follow the standard GitHub Community Guidelines. Be respectful, be constructive, and assume good intent.

How to Contribute

  1. Fork the repository you want to contribute to.
  2. Create a branch with a descriptive name (e.g., add-ublock-origin or fix-broken-link).
  3. Make your changes — add resources, fix errors, improve descriptions, or update outdated entries.
  4. Commit with a clear, concise message explaining what you changed and why.
  5. Open a Pull Request with a short description of your changes. Reference any related issues if applicable.

What Makes a Good Contribution

  • Quality over quantity. One well-researched, genuinely useful resource beats ten low-effort additions.
  • Stay on topic. Make sure your contribution fits the scope of the specific repository.
  • Respect licenses and copyrights. Only submit content you have the right to share.
  • Keep formatting consistent. Match the style and structure already used in the list.

Suggesting New Resources

Not sure if a resource belongs? Open an issue first to discuss it. We're happy to help figure out the right fit.

Reporting Issues

Use the GitHub issue tracker on the relevant repository to:

  • Flag broken or outdated links
  • Report inaccurate descriptions
  • Suggest improvements to organization or structure

Please include enough detail for us to understand and reproduce the issue.

Review Process

Every PR is reviewed by a maintainer. We may ask for changes or clarifications — this is normal and part of keeping quality high. We aim to review contributions promptly.

Questions?

If you need help or have questions about contributing, reach out at robbie.github@gmail.com or open an issue. We're happy to help.