Enable GH Actions

[andreyzher]

I see you've started work on migrating to GitHub Actions. I had some workflows already done on a fork, so hopefully this can help.

There are 3 workflows defined:

• sanity.yaml
  • Sanity / Lint checks that don't require access to any credentials/secrets and can therefore be run for forked PRs
• molecule.yaml
  • Molecule scenario execution which requires secrets for Artifactory to be set - only runs from within the IBM org (ie branched, instead of forked)
  • Required secrets: ARTIFACTORY_URL, ARTIFACTORY_REPO, ARTIFACTORY_TOKEN
• release.yaml
  • When repository is tagged, publish the collection to Galaxy and create the GitHub release with the collection archive attached
  • This requires a secret called GALAXY_TOKEN to be set

This is different from the Travis pipeline which can't cope with PRs from forks and automatically publishes on merge to main - with this workflow, the maintainers would be responsible for creating the Git tag, which would then trigger the release/publish process.

[salob]

Hi @andreyzher. Thanks for this contribution. We are only getting to review this now so could you please update your fork and have a look at the failing tests. We might create a develop branch that can be used for contributions instead of merging straight to main. Or would you have suggestions on this ?