-
Notifications
You must be signed in to change notification settings - Fork 212
Cherry-pick to master: Goodbye GitPod, hello GitHub Codespaces #507
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
Conversation
✅ Deploy Preview for nextflow-training ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Note that because of how we build the container, I think the file path |
8287643
to
116dea6
Compare
Decided it's not necessary
Tested most of the Hello Nextflow exercises, fixed a few remaining issues and updated setup instructions to recommend using a 4-core machine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks ready to go to me. Not merging myself bc if anything goes wrong I wouldn't know how to fix it, but anyone who's up early and feels good about it should feel free to merge.
Used
git cherry-pick
to lift changes in #506 over to be based on themaster
branch instead.Had to merge a bunch of conflicts manually - some version of #506 will still be needed for the new materials on that branch. Can update once this is merged and apply.
Still to do: