First off, thank you for considering contributing to BTXS! Your help is invaluable in making this project better. This document provides guidelines to ensure a smooth and effective contribution process.
- Ensure the bug was not already reported by searching on GitHub under Issues.
- If you're unable to find an open issue addressing the problem, open a new one. Be sure to use the "Bug Report" template and include as much detail as possible.
- We are always looking for ideas to improve BTXS!
- Please check the Issues to see if your idea has already been discussed.
- If not, open a new issue using the "Feature Request" template.
We welcome pull requests for bug fixes and feature enhancements. Please follow these steps to have your contribution considered:
- Fork the repository to your own GitHub account.
- Clone your fork to your local machine:
git clone https://github.com/BlackTechX011/BTXS.git - Create a new branch for your changes:
git checkout -b feature/my-amazing-featureorfix/a-specific-bug. - Make your changes. Ensure you adhere to the project's coding style by running
go fmt ./...andgoimports -w .within theBTXS/directory. - Update Documentation. If you add or change a command or flag, please update the relevant help text in
main.goand, if necessary, theREADME.md. - Commit your changes with a clear and descriptive commit message.
- Push your branch to your fork:
git push origin feature/my-amazing-feature. - Open a Pull Request to the
mainbranch of theBlackTechX011/BTXSrepository. Provide a clear title and description for your changes.
BTXS is distributed under a custom End-User License Agreement (EULA), not a standard open-source license. Please review the LICENSE.md file carefully.
By submitting a pull request, you certify that:
- (a) You have the right to submit the contribution, and it does not violate any third-party rights.
- (b) You agree that your contribution will be licensed under the same terms as the existing BTXS EULA.
- (c) You understand and agree that your contribution is subject to the same restrictions, including the prohibition on commercial use without permission and the naming requirements for derivative works.
This ensures that the project remains consistent and legally sound. We appreciate your understanding and cooperation.