jecs/docs/contributing/guidelines.md

# Contribution Guidelines

Whether you found an issue, or want to make a change to jecs, we'd love to hear back from the community on what features you want or bugs you've run into.

There's a few different ways you can go about this.

## Creating an Issue

This is what you should be filing if you have a bug you want to report.

[Click here](https://github.com/Ukendio/jecs/issues/new/choose) to file a bug report. We have a few templates ready for the most common issue types.

Additionally, see the [Submitting Issues](/contributing/issues) page for more information.

## Creating a Pull Request

This is what you should be filing if you have a change you want to merge into the main project.

[Click here](https://github.com/Ukendio/jecs/compare) to select the branch you want to merge from. 

Additionally, see the [Submitting Pull Requests](/contributing/pull-requests) page for more information.
docs: cleanup todo stubs, add code coverage reports, add examples, and pin introduction section (#227) * Allow pre existing hooks for observer * Cleanup some todo stubs * move coverage reports * use better link for addons * code coverage page * make Introduction sidebar visible on all pages and add a few relevant sections --------- Co-authored-by: Ukendio <ukendio@gmail.com> 2025-05-17 20:35:00 +00:00			`# Contribution Guidelines`
Start Work on Documentation (#74) * init bug / feat templates * capital J for style * PR templates * Combine templates because github be like that * Out with the old * package and package lock files * Deploy docs workflow * Absolutely massive commit (docs) * Delete cache and add to gitignore * Goodbye cache 2024-07-13 23:06:50 +00:00
docs: cleanup todo stubs, add code coverage reports, add examples, and pin introduction section (#227) * Allow pre existing hooks for observer * Cleanup some todo stubs * move coverage reports * use better link for addons * code coverage page * make Introduction sidebar visible on all pages and add a few relevant sections --------- Co-authored-by: Ukendio <ukendio@gmail.com> 2025-05-17 20:35:00 +00:00			`Whether you found an issue, or want to make a change to jecs, we'd love to hear back from the community on what features you want or bugs you've run into.`

			`There's a few different ways you can go about this.`

			`## Creating an Issue`

			`This is what you should be filing if you have a bug you want to report.`

			`[Click here](https://github.com/Ukendio/jecs/issues/new/choose) to file a bug report. We have a few templates ready for the most common issue types.`

			`Additionally, see the [Submitting Issues](/contributing/issues) page for more information.`

			`## Creating a Pull Request`

			`This is what you should be filing if you have a change you want to merge into the main project.`

			`[Click here](https://github.com/Ukendio/jecs/compare) to select the branch you want to merge from.`

			`Additionally, see the [Submitting Pull Requests](/contributing/pull-requests) page for more information.`