GIT-2023: Enable GitHub Actions support

[harshanarayana]

FOR RELEASE AFTER 21.3

closes #2023

Possible Issues

1. Unable to Retry individual test from a workflow. (Add ability to re-run single jobs actions/runner#432)

[codecov]

Codecov Report

Merging #2050 (9c7cf54) into main (5ba43de) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main     #2050   +/-   ##
=========================================
  Coverage   92.133%   92.133%           
=========================================
  Files           38        38           
  Lines         3470      3470           
  Branches       572       572           
=========================================
  Hits          3197      3197           
  Misses         185       185           
  Partials        88        88           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5ba43de...9c7cf54. Read the comment docs.

[ahopkins]

looks like a good start. I'll pop in with some of my ideas later.

[ahopkins]

Looks good to me.

[ahopkins]

Can you add a release workflow that copies the one in sanic-router? Release to PyPI on creation of a new release tag in GH.

[harshanarayana]

Can you add a release workflow that copies the one in sanic-router? Release to PyPI on creation of a new release tag in GH.

Yes. I will do that. I am actually considering creating an entirely new action dedicated just for sanic repo in general. Let me see how that effort goes.

[ahopkins]

What do you mean?

[harshanarayana]

> What do you mean?

@ahopkins Instead of defining the github actions in each repo, I would rather create a series of reusable action and leverage them across for all sanic-org projects.

- name: Run ${{ matrix.action }} on ${{ matrix.python-version }}
  uses: sanic-org/sanic-actions@v2
  with:
    python-version: ${{ matrix.python-version }}
    action: ${{ matrix.action }}

This is all you need to include in your github workflow with right set of python Version + os matrix. We can have a reusable set of actions in sanic-org/sanic-actions and reuse them everywhere.

[ahopkins]

@harshanarayana What is left to get this one going?

[harshanarayana]

@harshanarayana What is left to get this one going?

I just need to restructure this to use the new actions setup and then some minor workflow naming. A bit held up on office work for today and tomorrow. I will get this done and update the PR in another 2 days,.

[ahopkins]

Sounds great.

[harshanarayana]

@ahopkins once we merge this, let us start by setting all the test from workflow as an optional test and run it for a while to see if there are any other kinks that need to be sorted before we take travis out and then configure the mandatory test pass criteria. Does that sound okay to every @sanic-org/core-devs

[harshanarayana]

For now, I have added an optional way to configure the test retires and mark certain test for ignoring the failure like we did in Travis. BUt I am yet to find a clean way to mark the failed but ignored test as warning.

[ahopkins]

@ahopkins once we merge this, let us start by setting all the test from workflow as an optional test and run it for a while to see if there are any other kinks that need to be sorted before we take travis out and then configure the mandatory test pass criteria. Does that sound okay to every @sanic-org/core-devs

Yup. That was the plan.