Mr. Walls

First attempt at CI Testing #204

2

First attempt at laurent22/rsync-time-backup#204 - [x] tests run every time code is pushed to github (auto-tests) - [x] tests show passing example (just a test that usage is output when...

FEATURE: CI-Testing via github's actions (PR#205 READY FOR REVIEW)

2

To setup for laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ ###...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ > -...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ > -...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ - [...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ > -...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ > -...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ > -...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ > -...

Part of laurent22/rsync-time-backup#193 ## So that it's documented somewhere: CI Testing is great for ensuring code works and changes don't introduce regressions to tested code _(caveat: test coverage)_ > -...