Issue #148 - add a basic github release workflow.

[svogt0511]

Purpose

To use github actions for our workflows instead of Travis-CI.

Additional work here. Ruby must be updated.

closes: issue #148

Approach

Used lupo as a template.

Turned off rubocop for now. I will add a ticket for using it in the workflows. It has never been run on sashimi before. I did a test run and there were over 1000 issues, hundreds of which cannot be fixed automatically. Those that were fixed automatically broke the testing. (Added issue #150 )

Open Questions and Pre-Merge TODOs

Learning

Types of changes

• Bug fix (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 change)

Reviewer, please remember our guidelines:

• Be humble in the language and feedback you give, ask don't tell.
• Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
• Offer suggestions on how to improve code e.g. simplification or expanding clarity.
• Ensure you give reasons for the changes you are proposing.

[richardhallett]

Looks good. You might get problems with the slack notification, I think this job we use is out of date and I've ended up disabling for now until we look at a replacement.

[jrhoads]

Looks good.

I would argue that there is a place for both testing on PR and testing on explicit workflow dispatch but given a choice PR is more important.