Setup auto release workflow

[smoia]

Closes #311 and closes #239

Second attempt to integrate auto as a workflow, this time as a GitHub action. IF this works, we have a great automated workflow from PR merge to Pypi package (with the other workflow).

Proposed Changes

• Add .autorc configuration file
• Add github workflow that * should * retrieve the latest version of auto (might not be elegant) and then run it
• Add a couple of badges.

I can't wait to see if this works. So exciting!

@hipstersmoothie, could you please have a look at this PR?
@yarikoptic and @jwodder, you could have a look into this too - if you implemented a different solution I'd like to compare them, and otherwise if this works it should help you with datalad/datalad#4999 and dandi/dandi-cli#252!

[codecov]

Codecov Report

Merging #313 into master will decrease coverage by 1.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #313      +/-   ##
==========================================
- Coverage   95.85%   94.78%   -1.07%     
==========================================
  Files          29        9      -20     
  Lines        2314      844    -1470     
==========================================
- Hits         2218      800    -1418     
+ Misses         96       44      -52     

Impacted Files	Coverage Δ
D:/a/1/s/phys2bids/interfaces/txt.py
D:/a/1/s/phys2bids/tests/test_utils.py
D:/a/1/s/phys2bids/utils.py
D:/a/1/s/phys2bids/tests/test_physio_obj.py
D:/a/1/s/phys2bids/bids.py
D:/a/1/s/phys2bids/viz.py
D:/a/1/s/phys2bids/tests/test_bids.py
D:/a/1/s/phys2bids/due.py
D:/a/1/s/phys2bids/phys2bids.py
D:/a/1/s/phys2bids/tests/test_viz.py
... and 10 more

[smoia]

(BTW, I set up the GH_TOKEN as an organisation secret. Is that right?)

[eurunuela]

I guess this looks good. I don't think I'm the best person to review this PR though.

[tsalo]

Is this still valid when phys2bids is past alpha (i.e., 1.0.0+)?

[smoia]

We could remove it, but honestly it' mainly there to maintain the same configuration across physiopy. I doubt we'll ever use that label!

[tsalo]

My review is basically the same as @eurunuela's. I read through everything and it makes sense, but since I'm not familiar with auto, I'm not sure how valuable my review is.

(BTW, I set up the GH_TOKEN as an organisation secret. Is that right?)

That seems reasonable. It looks like you need to add your personal access token to the GitHub repository's secret environmental variables. I'm not sure if organization-level secrets are automatically used for individual repositories, but it makes sense that they would be.

[smoia]

This is what I did for the secrets (They are both linked to my account)

[eurunuela]

I say we give this a shot if you feel comfortable with it @smoia

[smoia]

Ok, let's try this out.

[smoia]

🚀 PR was released in 2.2.1 🚀