Contributing
Last updated
Last updated
We welcome contributions to TheNewEconomy plugin and appreciate your efforts to improve the project! Before getting started, please take a moment to review these guidelines to help streamline the process and ensure consistency across contributions.
To maintain a consistent codebase, please adhere to the following style guidelines:
1. Import the Code Style
Use the code style defined in the file. You can import this file into your IntelliJ environment by following these steps:
Navigate to File -> Settings -> Editor -> Code Style.
Click on the gear icon and select Import Scheme.
Choose IntelliJ IDEA code style XML and select the TNE_Style.xml file located in the .contributing/ folder.
This will ensure that your code adheres to the project's formatting rules.
2. Final Obsession IntelliJ Plugin
We recommend using the Final Obsession plugin to ensure that all applicable variables, fields, and method parameters are declared final where appropriate. This helps maintain immutability, enhancing code safety and readability.
Installation:
In IntelliJ, go to File -> Settings -> Plugins.
Search for the plugin .
Click Install.
Restart IntelliJ to activate the plugin.
Before submitting your first pull request, you must sign our Contributor License Agreement (CLA). This is required to ensure that we can freely use your contributions while maintaining the integrity of the project's licensing.
To help organize the development process, we follow specific conventions for branch names based on their purpose:
Feature branches are used to develop new features. Use the prefix feature/ or feat/.
Example: feature/login-system or feat/payment-processing.
Bugfix branches are used to fix bugs in the code. Use the prefix bugfix/ or fix/.
Example: bugfix/header-styling or fix/form-validation.
Hotfix branches are created directly from the production branch to fix critical bugs in the production environment. Use the prefix hotfix/ or hfix/.
Example: hotfix/critical-security-issue or hfix/performance-patch.
Release branches are used to prepare for a new production release. They allow for last-minute adjustments and polishing. Use the prefix release/.
Example: release/v1.0.1.
Fork the repository to your own GitHub account.
Clone the forked repository to your local machine.
Create a new branch for your changes using the branch naming guidelines above.
Commit your changes with clear and descriptive commit messages.
Push your changes to your fork.
Create a pull request (PR) with a detailed explanation of your changes and any relevant issues.
Please ensure that your pull request is current with the latest version of the main branch before submission.
After submitting your pull request, one of the maintainers will review your changes. You may be asked to make adjustments or provide further clarification. Once approved, your changes will be merged into the main repository.
Thank you for your contribution!
All new contributions to this project will be licensed under the license. By contributing, you agree that your contributions will also be licensed under this license.