Pull requests are welcome. Ideally first state the problem or feature you need and engage in a discussion on gitter or github issues. A high level design discussion will be needed for new features.
The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch. The rules are pretty simple: if you can certify the below (from developercertificate.org):
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
660 York Street, Suite 102,
San Francisco, CA 94110 USA
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
then you just add a line to every git commit message:
Signed-off-by: Joe Smith <joe.smith@email.com>
using your real name (sorry, no pseudonyms or anonymous contributions.) and an e-mail address under which you can be reached (sorry, no github noreply e-mail addresses (such as username@users.noreply.github.com) or other non-reachable addresses are allowed).
On the command line you can use git commit -s to sign off the commit.
The workflow in .github/workflows/build.yml builds the solution, runs unit tests, and runs local integration tests without cloud credentials. Fork PRs use the normal pull_request event and wait for approval under the repository's Require approval for all external contributors policy.
Cloud integration tests and SonarCloud run automatically on pushes to master and release/*. Manual cloud validation from a trusted branch requires approval through the integration-tests environment. An optional PR number and full reviewed head SHA select an immutable contributor commit; the PR must include the selected trusted branch and still have the same head after approval.
See Continuous integration for the job matrix, repository settings, credential scope, and manual validation instructions. Configure the stable CI check as required for merges; cloud/Sonar jobs deliberately do not run on PR events.