First off, thank you for considering contributing to the Mifos Gazelle Demo Runtime! It's people like you that make the open-source community such a great place. We welcome any form of contribution, from reporting bugs and requesting features to submitting code changes.
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open-source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
This is one of the most helpful ways to contribute. If you find a bug, please ensure the bug was not already reported by searching on jira under gax-27.
If you're unable to find an open issue addressing the problem, open a new ticket. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
If you have an idea for an enhancement or a new feature, please open an issue to discuss it. This allows us to coordinate our efforts and prevent duplication of work.
When creating an enhancement suggestion, please:
- Use a clear and descriptive title to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Explain why this enhancement would be useful to most users.
The process described here has several goals:
- Maintain project quality
- Fix problems that are important to users
- Engage the community in working toward the best possible solution
- Enable a sustainable system for maintainers to review contributions
- Fork the repo on GitHub.
- Clone your fork locally:
git clone [https://github.com/your_username/mifos-gazelle-demo-runtime.git](https://github.com/your_username/mifos-gazelle-demo-runtime.git)
- Create a feature branch for your local development:
Now you can make your changes locally.
git checkout -b name-of-your-bugfix-or-feature
- Commit your changes using a descriptive commit message:
git commit -m "feat: Add some feature" - Push your branch to your fork on GitHub:
git push origin name-of-your-bugfix-or-feature
- Open a Pull Request from your fork to the original
mainbranch. Provide a clear title and description for your pull request, explaining the "what" and "why" of your changes.
- Follow the existing code style.
- Write clear, commented code where necessary.
- Ensure your code is readable and maintainable.
We look forward to your contributions!