-
Notifications
You must be signed in to change notification settings - Fork 2
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
Move out integration processes #597
Conversation
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.
I think there a few more things we need to do here before merging, so we still have a working workflow... Mostly we need to either remove or rename some things so that we are not calling processes that the script does not know about. (The alternative would be to import the module, but I don't think that is the direction we want to go at this point).
integrate.nf
Outdated
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.
Do you want to rename this while you are at it, since it isn't integration at all now?
integrate.nf
Outdated
@@ -180,4 +129,3 @@ workflow { | |||
// generate integration report | |||
integration_report(integrate_harmony.out, file(integration_template)) |
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.
Probably want to rename this report, and we need to get rid of the integration process calls above here?
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.
Maybe just comment this out for now, since we also don't have the rmd
yet?
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.
Yeah, I'm fine with just commenting out most of this. I just don't like the idea of merging in changes that by their nature break the workflow.
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.
and we need to get rid of the integration process calls above here?
Ah, I totally missed this 🙃. I blame my long 🦃 break. These lines are gone now!
👏 |
In actual response to your feedback here, I was wary about going too far here and making |
…TODOs where those updates are on likely deprecated code
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.
Apparently github felt this update was sufficiently different to call it a whole new file instead of a diff!
Let me know what you think of this now! I made some changes to get |
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.
LGTM, but might as well add in the missing stub chunk!
Co-authored-by: Joshua Shapiro <[email protected]>
Closes #592
A little 🍬 to get the ball rolling! This PR does what it says.