Closed cansavvy closed 3 years ago
👍 I don't think we're going to be able to go through HTML preview thoroughly during review. I think we're better served by getting this merged and then filing individual issues (or PRs) as we find issues.
Makes sense to me.
Changes Being Published
We're publishing everything that's in staging. This is mostly polishing PRs #289 and #290, but also includes adding the RNA-seq pathway analyses.
This will close #390 and #391
List of Commits/PR's Included
Highlights are that the RNA-seq pathway analyses have been added:
394 #395 - ORA for RNA-seq
405 #408 - GSEA for RNA-seq
403 #404 - GSVA for RNA-seq
And the rest are a lot of polishing PRs as well as "make github louder" PR.
Link to html Preview
For reviewing purposes, you can take a browse through htmlpreview: http://htmlpreview.github.io/?https://github.com/AlexsLemonade/refinebio-examples/gh-pages-stages/01-getting-started/getting-started.html
Effectively every html has had some changes at this point.
Publishing Checklist:
[x] Does everything look good using html preview -- having taken a particularly close look at any new html files?
[x] Have any new examples been added to the refinebio-examples feedback survey? Ideally, don't click publish until this PR is merged (changes are autosaved).
Survey is updated but not published yet.