Thank you for considering contributing to LiteFM! We welcome all kinds of contributions including code, documentation, bug reports, feature requests, and more. This document outlines the process to help you get started.
By participating in this project, you agree to abide by our Code of Conduct. Please read it to understand the expectations we have for everyone who participates in the project.
If you find a bug in the project, please open an issue on our GitHub Issues page with the following information:
- A clear and descriptive title.
- Steps to reproduce the bug.
- Expected and actual behavior.
- Screenshots or logs if applicable.
- Any other relevant information.
We welcome new feature suggestions! To propose a feature, please:
- Check existing issues to see if the feature has already been requested.
- Open a new issue and describe the feature in detail.
- Explain why the feature would be beneficial.
If you're ready to contribute code, follow these steps:
- Fork the repository.
- Create a new branch:
git checkout -b feature/my-feature
. - Make your changes and commit them:
git commit -m 'Add some feature'
. - Push to the branch:
git push origin feature/my-feature
. - Open a pull request.
Check CLANG-FORMAT to understand how your code should align with the LiteFM code structure.
To run clang-format
:
clang-format -i src/*.c
clang-format -i include/*.h
clang-format lfm.c
Documentation improvements are always appreciated! You can:
- Improve existing documentation.
- Add new tutorials or guides.
- Fix typos or clarify language.
To set up your development environment:
- Clone the repository:
git clone https://github.com/nots1dd/litefm.git
- Navigate to the project directory:
cd litefm
- Follow the setup instructions in the
README.md
.
Warning
If you plan on building this manually,
Then ensure that you have all deps installed and working! (check README.md
for more)
- Follow the existing code style. (TABS AND PRETTY CODE PLS)
- Use meaningful variable and function names.
- Write comments where necessary, especially in complex code sections.
- When creating a new file, ensure that you follow the commenting system in place.
- Add a new version file in
CHANGELOG
file with the latest version.md in place - Ensure that you follow the format of
version.md
and list all important changes - The commit message MUST follow either
[COMMIT-TYPE] Small msg..
or[COMMIT-TYPE] CHANGELOG vX.Y
- Ensure your changes pass existing tests and do not break the build.
- Write or update tests as necessary.
- Submit your pull request with a clear description of your changes.
- Be prepared to make revisions based on feedback from maintainers.
We appreciate your contributions and look forward to working with you!