GitHub 29 recognizes a set of community health files and links them where contributors need them: CONTRIBUTING.md appears when someone opens an issue or pull request, and CODE_OF_CONDUCT.md in the repository's sidebar. Both may live in the root, docs/ or .github/. BookNest's guide says how to start, what a good pull request looks like, and how long a review takes:
# Contributing to BookNest
Thanks for helping! Bug reports, documentation fixes and small features are all welcome.
## Before you start
- Search the issues first; comment on one before starting anything larger than a small fix.
- Issues labeled `good first issue` are a good place to begin.
## Making a change
1. Fork the repository and create a branch from `main`, named after the change.
2. Start PostgreSQL with `docker compose up -d`, then run `npm install` and `npm test`.
3. Keep each pull request to one change, with tests for new behavior.
4. Open the pull request against `main` and fill in the template; link the issue (`Closes #12`).
A maintainer reviews within a week. Every conversation must be resolved before merging.
By taking part you agree to follow our [Code of Conduct](CODE_OF_CONDUCT.md).For the code of conduct, Sam adopts the Contributor Covenant 3.0 (released July 2025, CC BY-SA 4.0), filling in its reporting contact, conduct@example.com, and deleting its editor's notes. Pull request #11 adds both files. The community profile API (gh 29 api repos/{owner}/{repo}/community/profile) scores a repository against GitHub's checklist: BookNest went from 57% to 85%. The one item still missing is a quirk, because the profile did not count the YAML issue form from Issue Forms and Templates as an issue template.