ReconstructSPI Workflow Infrastructure

[thisFreya]

Files for Github workflow in reconstructSPI. Mostly adapted from ioSPI.

[thisFreya]

Tried to fix the codecov error but no dice - it should only be present in this commit as there is no actual code present.

[geoffwoollard]

Note that the tests were passing fine in #21

As soon as there is some code that gets tested, the test coverage will go up and a 0% test coverage error from init files won't arise.

[geoffwoollard]

Remove dependencies. Also do we want to have a dev branch? To see if the testing/linting runs we have to merge into master. And then as something breaks, master is broken.

[thisFreya]

Also do we want to have a dev branch? To see if the testing/linting runs we have to merge into master. And then as something breaks, master is broken.

@geoffwoollard Not sure what you mean by this, surely if the PR's have tests passing before they merge into master things shouldn't break?

[thisFreya]

Also do we want to have a dev branch? To see if the testing/linting runs we have to merge into master. And then as something breaks, master is broken.

Not sure what you mean by this, surely if the PR's have tests passing before they merge into master things shouldn't break?

@geoffwoollard I've added a branch "dev" to the requisite spots.

[geoffwoollard]

Also do we want to have a dev branch? To see if the testing/linting runs we have to merge into master. And then as something breaks, master is broken.

@geoffwoollard Not sure what you mean by this, surely if the PR's have tests passing before they merge into master things shouldn't break?

Yes yes good point! master won't break unless the failing tests in the PR are merged...