Contributing

We welcome contributions in several forms, e.g.

  • Sponsoring
  • Documenting
  • Testing
  • Coding
  • etc.

Please read 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star.

Please check for the issues in the project and look for unassigned ones or create a new one. The good issues for newcomers are marked with help-wanted and good-first-issue.

Working together in an open and welcoming environment is the foundation of our success, so please respect our Code of Conduct.

Guidelines

Workflow

We use the Feature Branch Workflow and review all changes we merge to master.

Automated builds, tests, security and code quality checks

The code is required to pass the automated build, all unit-tests must be green and the configured security- (snyk) and code quality (lgtm) checks must be OK before the pull request can be merged.

Commit Message

Commit messages shall follow the conventions defined by conventional-changelog.

The content of the community tools and libraries documentation pages is licensed under the MIT License.
Siemens API Notice applies.
Back to top