Skip to content

Latest commit

 

History

History
29 lines (19 loc) · 968 Bytes

File metadata and controls

29 lines (19 loc) · 968 Bytes

Contributing

Thanks for taking the time to improve one of my projects.

Good First Contributions

  • Fix unclear README sections or setup instructions.
  • Report reproducible bugs with logs, screenshots, or steps.
  • Suggest focused UX improvements.
  • Add small tests around existing behavior.

Before Opening a Pull Request

  1. Check existing issues and discussions to avoid duplicate work.
  2. Keep the change focused on one problem.
  3. Explain why the change is needed, not only what changed.
  4. Run the relevant checks for the project when possible.

Pull Request Checklist

  • The change has a clear summary.
  • Setup or usage docs were updated when behavior changed.
  • Tests or manual verification steps are included.
  • Secrets, API keys, personal data, and generated build artifacts are not committed.

Communication

For bugs, use Issues. For product ideas, design direction, or broader questions, use Discussions when the repository has it enabled.