Skip to content

Latest commit

 

History

History
72 lines (51 loc) · 1.87 KB

File metadata and controls

72 lines (51 loc) · 1.87 KB

Contributing to Rulefy

Thank you for considering contributing to Rulefy! This document provides guidelines and instructions for contributing.

Code of Conduct

By participating in this project, you agree to abide by its Code of Conduct.

How Can I Contribute?

Reporting Bugs

  • Check if the bug has already been reported in the Issues section
  • Use the bug report template to create a new issue
  • Include detailed steps to reproduce the bug
  • Include your environment details (OS, Node.js version, etc.)

Suggesting Enhancements

  • Check if the enhancement has already been suggested in the Issues section
  • Use the feature request template to create a new issue
  • Describe the enhancement in detail and explain why it would be useful

Pull Requests

  1. Fork the repository
  2. Create a new branch (git checkout -b feature/amazing-feature)
  3. Make your changes
  4. Run tests and linting (npm test && npm run lint)
  5. Commit your changes (git commit -m 'Add some amazing feature')
  6. Push to the branch (git push origin feature/amazing-feature)
  7. Open a Pull Request

Development Setup

  1. Clone the repository
  2. Install dependencies:
    npm install
    
  3. Build the project:
    npm run build
    
  4. Run tests:
    npm test
    

Styleguides

Git Commit Messages

  • 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 liberally after the first line

JavaScript/TypeScript Styleguide

  • Use 2 spaces for indentation
  • Use semicolons
  • Follow the ESLint configuration

Documentation Styleguide

  • Use Markdown for documentation
  • Reference examples when possible

License

By contributing, you agree that your contributions will be licensed under the project's MIT License.