Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do a staging -> master merge after GSVA is in #380

Closed
cansavvy opened this issue Nov 25, 2020 · 2 comments
Closed

Do a staging -> master merge after GSVA is in #380

cansavvy opened this issue Nov 25, 2020 · 2 comments
Labels
before going live Needs to be done before we can "go live" or do testing

Comments

@cansavvy
Copy link
Contributor

We've added a few new modules since the last staging -> master PR (#320). This is just a reminder that after GSVA is finished getting merged (#362), it would probably be a good time to port the changes to master (and once again check that this process works alright before we "go live" #286 ).

@jaclyn-taroni jaclyn-taroni added the before going live Needs to be done before we can "go live" or do testing label Nov 26, 2020
@cansavvy
Copy link
Contributor Author

cansavvy commented Dec 1, 2020

The strategy has changed some. I'm going to make separate issues to remind us to publish GSVA (#371) and GSEA (#354) after their intro paragraphs are done.

@cansavvy
Copy link
Contributor Author

cansavvy commented Dec 1, 2020

Now this can be closed after #389 and #384 are merged.

@cansavvy cansavvy closed this as completed Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
before going live Needs to be done before we can "go live" or do testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants