-
Notifications
You must be signed in to change notification settings - Fork 203
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
Update first release procedure #2640
base: main
Are you sure you want to change the base?
Conversation
❌ Deploy Preview for nf-core-main-site failed. Why did it fail? →
|
sites/docs/src/content/docs/tutorials/adding_a_pipeline/first_release.md
Show resolved
Hide resolved
@nf-core-bot fix linting pretty please 🙏 |
So if I understand this correctly, the PR shows you the differences to the latest template release which may not be in master, making sure you're only reviewing changes between your pipeline and template instead of the changes between the old version of the template and new version of the template and pipeline changes? |
sites/docs/src/content/docs/tutorials/adding_a_pipeline/first_release.md
Outdated
Show resolved
Hide resolved
…release.md Co-authored-by: James A. Fellows Yates <[email protected]>
Has anyone checked this process to make sure that it definitely works, with merge conflicts etc? |
@@ -37,10 +37,15 @@ Not to worry, we're a friendly bunch. | |||
|
|||
To get your pipeline reviewed for its initial release, do the following: | |||
|
|||
1. Make a pull-request from the `dev` branch to `master` on the nf-core fork. This is a | |||
1. Create a new branch based on `TEMPLATE`, called `TEMPLATE_<TOOLS_VERSION>` from the version of the TEMPLATE (i.e., latest tools sync) that is in the `dev` branch you wish merge into `master`. |
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.
why not make the PR directly against TEMPLATE
?
No description provided.