Sonar Documentation
  • Become a Patreon
  • Join the Discord
  • Sonar
    • Welcome
    • Getting started
    • Supported versions
    • Translations
  • Administration
    • Commands and Permissions
    • Usage of MiniMessage
    • Configuring Sonar
      • General settings
      • Adjusting the attack tracker
      • Setting up a database
      • Configuring the verification
        • Using 1.20.5+ transfers
  • Development
    • Working with the API
    • Building
  • Contributing
    • Guidelines
    • Pull Requests
    • Bug Reports
    • Feature Requests
Powered by GitBook
On this page
  • Contributing Guidelines
  • Coding Guidelines
  1. Contributing

Guidelines

PreviousBuildingNextPull Requests

Last updated 1 year ago

Contributing Guidelines

  1. Fork the repository and create a new branch for your contribution.

  2. Follow the coding guidelines for your code.

  3. Test your code before committing and pushing it.

  4. Use commit messages for your commits.

Coding Guidelines

  • Use the same code style and formatting as the rest of the project.

    • Optional: Use an IDE that supports .editorconfig files.

  • Use meaningful names for variables, classes, and methods.

  • Write clear comments to explain complex parts of your code.

  • Ensure your code is easy to read and maintain.

semantic