Codecov Report

Merging #970 (6770376) into master (4a12af0) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #970   +/-   ##
=======================================
  Coverage   81.30%   81.30%           
=======================================
  Files         139      139           
  Lines       15150    15150           
=======================================
  Hits        12317    12317           
  Misses       2833     2833           

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 4a12af0...6770376. Read the comment docs.

From a review comment from @sroet (buried in a resolved conversation), regarding the OPS tag on http://mattermodeling.stackexchange.com:

Also, how can we (as experienced users) sign up for email updates on these tags?

A couple options for subscribing, from the current StackExchange UI:

1. Create a custom filter notification. Filter on the openpathsampling tag to create a filter for all questions tagged with openpathsampling across the entire StackExchange network (obviously, there's only one site with that tag right now). Choose email notifications to get the email. You can narrow by site (if, for example, you wanted to see python-tagged questions on mattermodeling.SE without drowning in the firehose from SO).

2. You can also subscribe to any tag with RSS: On any question that has a given tag, hover over the tag. At the top-right of the thing that appears on hover, you'll see the RSS icon. Click on that to get the URL for an RSS feed for that tag on that site (gives more flexibility in how to manage notifications than email).

(Note: the only question currently tagged with openpathsampling is a placeholder so the tag doesn't get auto-deleted -- it isn't related to OPS. Over the weekend I answered good questions from emails from a couple users and I've asked them to re-post there. So I hope we'll see a few real questions soon.)

This is ready for review and comment. I will leave it open for at least 24 hours, merging no earlier than Thu 10 Jun 18:00 GMT (14:00 my local).

I've tested the new deploy_docs workflow within the docs_deploy branch -- it works, as can been seen at this actions link (for the next 90 days), or simply from the fact that openpathsampling.org is reporting OPS version 1.4.3.dev0 as the latest development version (as opposed to 1.4.1.dev0, as it was before).

Thanks to @jchodera for meeting this morning to get the AWS stuff set up!

@dwhswenson Did it work?

@jchodera : Yep -- everything went perfectly smoothly. Thanks again for your help!

I added a new workflow to handle building/deploying docs. This will replace our old after_success script, and will allow us to have better control over when we want to build/deploy docs. That's the only place the new env secrets need to be used. This also adds extra security: a breach like the CodeCov breach should not affect the AWS secrets, because they're not used in the same workflow step (or even the same workflow). The same was true of our PyPI secrets -- although I rotated them after the CodeCov breach anyway.