Add a job to build and test the Python module (just using python setup.py build, python setup.py test, as in the README).
Add a job to build and test the Bazel build (bazel build //cmd:all, bazel test //..., as in the README)
The Travis workflow included building and running the Python module, and it seems worth replicating that in the new GitHub build-and-test workflow. I think the Bazel build is worth checking as well.
This PR also includes a commit that removes some unnecessary empty prebuild steps from the workflow configuration (which I should have cleaned up right at the start before merging the workflow config initially, but never mind).
For #1121:
python setup.py build,python setup.py test, as in the README).bazel build //cmd:all,bazel test //..., as in the README)The Travis workflow included building and running the Python module, and it seems worth replicating that in the new GitHub build-and-test workflow. I think the Bazel build is worth checking as well.
This PR also includes a commit that removes some unnecessary empty prebuild steps from the workflow configuration (which I should have cleaned up right at the start before merging the workflow config initially, but never mind).