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

Add option to specify UMI separator in extract 2 #549

Closed
wants to merge 1 commit into from
Closed

Add option to specify UMI separator in extract 2 #549

wants to merge 1 commit into from

Conversation

janoppelt
Copy link
Contributor

Add option to specify UMI separator in umi_tools extract. The default stays as it is now ("_"). Allows users to change it to other strings. 2

Add option to specify UMI separator in umi_tools extract. The default stays as it is now ("_"). Allows users to change it to other strings.
@IanSudbery
Copy link
Member

Hi @TomSmithCGAT can we set up the CI to run on PRs as well as commits?

@opplatek This looks good, but I'll need to run our tests.

@TomSmithCGAT
Copy link
Member

I just need to finish off #546 (add py 3.5) and then merge and it should run on all pushes

I've blocked out tomorrow for just UMI-tools so I'll do this first thing and then try and resolve the deterministic issues

@TomSmithCGAT
Copy link
Member

Merged #546 and set to run CI on PRs and pushes. Need to work out how to get it to run on an existing PRs now though...
If all else fails, I guess it's a re-issue PR or add new commit with e.g empty line

@TomSmithCGAT TomSmithCGAT reopened this Aug 4, 2022
@TomSmithCGAT
Copy link
Member

💡 Just need to close and re-open and github treats it as a new PR 😁

@TomSmithCGAT
Copy link
Member

TomSmithCGAT commented Aug 4, 2022

@opplatek - Am I right in understanding that the two PRs from your patch-1 and patch-2 branches both need to be merged? I don't think the testing is appropriate for the separate PRs:

  • patch-1 fails the tests because of an issue resolved in patch-2
  • patch-2 passes the tests because it doesn't have any effect without the changes in patch-1

Could you please merge the two patches and issue a new PR 🙏 Thank you!

@janoppelt
Copy link
Contributor Author

Hi @TomSmithCGAT . Sorry for the confusion. The new push of the changes is at #551.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants