Thank you for your interest in contributing to Abeille! This document provides guidelines and instructions for contributing.
By participating in this project, you agree to maintain a respectful and inclusive environment for everyone.
Bugs are tracked as GitHub issues. Create an issue on the repository and provide the following information:
- Use a clear and descriptive title
- Describe the exact steps to reproduce the problem
- Provide specific examples (including configuration files or commands used)
- Describe the behavior you observed and why it is a problem
- Include screenshots and animated GIFs if possible
- Include details about your environment
Enhancement suggestions are also tracked as GitHub issues. When creating an enhancement suggestion:
- Use a clear and descriptive title.
- Provide a detailed description of the suggested enhancement.
- Explain why this enhancement would be useful to most users.
- List some other applications where this enhancement exists, if applicable.
Unsure where to begin? Feel free to ask!
- Do not include issue numbers in the PR title
- Follow the coding style and use linter
- Document new code based on the project's documentation style
- End all files with a newline
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests after the first line
- Use 2 spaces for indentation
- Prefer
constoverlet - Use PascalCase for interfaces, types, and classes
- Use camelCase for functions and variables
- Add appropriate JSDoc comments for public APIs
- Follow eslint configuration rules
- Fork the repo and create your branch from
master - Install dependencies with
bun install - Make your changes
- Ensure your code lints with
bun lint - Submit your pull request
By contributing to Abeille, you agree that your contributions will be licensed under the project's license.