GitHub Actions setup

[ErwanGauduchon]

Proposed changes

Replace Travis CI with GitHub Actions.

Types of changes

What types of changes does your code introduce to this plugin?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Issues closed by changes

• Close Update the CI/CD process to use GitHub Actions #17

Checklist

• I have read the CONTRIBUTING doc
• I agree with the CODE OF CONDUCT
• Lint and unit tests pass locally with my changes
• SonarCloud and Travis CI tests pass with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information