change nf-EAGER to nf-core/EAGER2 #15
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Can you update this one with EAGER2.0 -> EAGER2? |
Member
Author
|
Only if you rename that one too: |
Member
Author
|
Sorry, manage to click on the close while rebasing, so I can't reopen, so I'm making a new PR... |
Member
|
Np, container is up here: https://hub.docker.com/r/nfcore/eager2/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would change the name of the repo from EAGER2.0 to EAGER2.
That would make more changes, but it would make more sense.
I think also we can refer to EAGER2 instead of nf-core/EAGER2 in most of the cases.
But I prefer to have @apeltzer decide for that ;-).