chore: add missing files

[xixas]

Description

• Added code of conduct
• Added Contributing
• Added PR Template

Summary by CodeRabbit

• Documentation
  • Updated the pull request checklist to include preliminary unit testing.
  • Added a selection mechanism for different pull request templates.
  • Introduced a Contributor Covenant Code of Conduct.
  • Provided new contribution guidelines for the project.

[coderabbitai]

Warning

Rate Limit Exceeded

@xixas has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 43 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between fdef03d and 66c861f.

Walkthrough

This update introduces new templates and guidelines to streamline contributions and maintain a positive community environment. It includes changes to the pull request process, the addition of a code of conduct, and detailed contribution guidelines.

Changes

File Path	Change Summary
.github/.../pull_request_template_api.md	Updated the testing step in the API template's pull request checklist.
.github/pull_request_template.md	Added a selection mechanism for different sub-templates in the Preview tab.
CODE_OF_CONDUCT.md	Introduced a code of conduct to outline expected behavior and enforcement.
CONTRIBUTING.md	Provided comprehensive guidelines for contributing to the project.

Possibly related issues

• Setup CONTRIBUTING.md file document-service#21: The creation of CONTRIBUTING.md in this PR directly addresses the objectives of establishing clear contribution guidelines and processes.

🐇✨📜
In the garden of code, where ideas bloom,
We've laid new paths and swept with our broom.
🌟 For every coder, new or adept,
A guide, a template, promises kept.
Hop along, let's make our code gleam!
🐾

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 25

Out of diff range and nitpick comments (8)

.github/pull_request_template.md (1)

4-4: Ensure the file ends with a newline character to comply with POSIX standards.

Please add a newline character at the end of the file.

.github/PULL_REQUEST_TEMPLATE/pull_request_template_api.md (1)

6-6: Ensure consistency in capitalization within the document.

Consider capitalizing "api docs" to maintain consistency with other document titles.

CODE_OF_CONDUCT.md (2)

119-119: Use a markdown link for bare URLs to improve readability.

Consider using a markdown link for the URL to improve the document's readability and appearance.

---

128-128: Ensure the file ends with a newline character to comply with POSIX standards.

Please add a newline character at the end of the file.

CONTRIBUTING.md (4)

28-28: Start the sentence with an uppercase letter.

Consider starting the sentence with an uppercase letter to maintain consistency and formality in the document.

---

239-239: Add a period after "etc" to comply with American English conventions.

Consider adding a period after "etc" to align with American English punctuation rules.

---

246-246: Add a period after "etc" to comply with American English conventions.

Consider adding a period after "etc" to align with American English punctuation rules.

---

276-276: Ensure the file ends with a newline character to comply with POSIX standards.

Please add a newline character at the end of the file.