Thank you for contributing to Aqueduct. We welcome contributions via New Issues, Pull Requests, and Feature Requests.
Please read the Code of Conduct we use and sign a CLA before submitting contributions.
If you find something wrong or broken, please file an issue with label new-issue
. Please include a minimum explanation for how to repro your issue. At the very least include:
-
Current dev environment (OS version, Tools version, Aqueduct version).
-
Steps to reproduce the bug.
Your bug will be triaged (answer-in-docs
, already-filed
, new bug
) and moved forward.
Please start off by opening an issue or adding to the discussion of an existing one. That way, we’re all on the same page before your PR lands.
Several things to make it easier for us to accept your PR:
-
Tackle one bug or feature at a time.
-
Keep to the coding style and conventions already there.
-
Don't break anything!
The reviewers will then work with you to get your idea in to main.
We’re keen to hear your ideas for improving and extending Aqueduct. Please file an issue with label feature-request
. We will triage all ideas with respect to Aqueduct’s roadmap and resources.
You need to sign a Contributor License Agreement (CLA) to accept your pull request. You only need to do this once. If you submit a pull request for the first time, please get in touch with us at [email protected]. Put "CLA Individual" in the Subject: line.
If you make contributions to our repositories on behalf of your company, we will need a Corporate Contributor License Agreement (CLA) signed. To do that, please get in touch with us at [email protected]. Put "CLA Corporate" in the Subject: line.