👍 First off, thank you for taking the time to contribute! 👍
The following is a set of guidelines for contributing to HELICS and associated projects. These are suggested guidelines. Use your best judgment.
HELICS is distributed under the terms of the BSD-3 clause license. All new contributions must be made under this LICENSE in accordance with the Github terms of service, which uses inbound=outbound policy. By submitting a pull request you are acknowledging that you have the right to license your code under these terms.
If you just have a question check out
This section guides you through submitting a bug report for the containers library. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
When you are creating a bug report, please include as many details as possible. Frequently, helpful information includes operating system, version, compiler used, API, interface, and some details about the function or operation being performed.
Note: If you find a Closed issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
Typically you would want to submit a pull request against the develop branch. That branch gets merged into master periodically but the develop branch is the active development branch where all the code is tested and merged before making a release. There is a Pull request template that will guide you through the needed information.