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.

Sign up for GitHub

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

Jump to bottom

Fix to issue 299 and 297 #300

Merged
merged 8 commits into from Mar 13, 2024
Merged

Fix to issue 299 and 297 #300

merged 8 commits into from Mar 13, 2024

Conversation

heylf
Copy link
Contributor

@heylf heylf commented Feb 2, 2024

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
  • If necessary, also make a PR on the nf-core/scrnaseq branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core lint).
  • Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
  • Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 2, 2024

This PR is against the master branch ❌

  • Do not close this PR
  • Click Edit and change the base to dev
  • This CI test will remain failed until you push a new commit

Hi @heylf,

It looks like this pull-request is has been made against the heylf/scrnaseq master branch.
The master branch on nf-core repositories should always contain code from the latest release.
Because of this, PRs to master are only allowed if they come from the heylf/scrnaseq dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page.
Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

@heylf
Copy link
Contributor Author

heylf commented Feb 2, 2024

This PR should fix the issues 297 and 299

@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 2, 2024 •
edited

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit e20e897

+| ✅ 171 tests passed       |+
#| ❔   4 tests were ignored |#
!| ❗   3 tests had warnings |!

❗ Test warnings:

  • pipeline_todos - TODO string in main.nf: Optionally add in-text citation tools to this list.
  • pipeline_todos - TODO string in main.nf: Optionally add bibliographic entries to this list.
  • pipeline_todos - TODO string in main.nf: Only uncomment below if logic in toolCitationText/toolBibliographyText has been filled!

❔ Tests ignored:

✅ Tests passed:

Run details

  • nf-core/tools version 2.13.1
  • Run at 2024-03-13 07:08:03

grst
grst requested changes Feb 2, 2024
View reviewed changes
modules/local/mtx_to_seurat.nf Outdated Show resolved Hide resolved
@heylf heylf changed the base branch from master to dev February 2, 2024 14:21
@grst
Copy link
Member

grst commented Feb 14, 2024

Now that @fmalmeida set-up nf-test, it would be great to add a testcase for cellranger-arc to make sure such issues don't arise again.

@heylf
Copy link
Contributor Author

heylf commented Feb 15, 2024

Now that @fmalmeida set-up nf-test, it would be great to add a testcase for cellranger-arc to make sure such issues don't arise again.

I agree. I assigned myself to that issue. I will do it latest before the March Hackathon.

@grst grst mentioned this pull request Mar 5, 2024
Merged
@grst
Copy link
Member

grst commented Mar 7, 2024

@heylf, could you please take another look? I'm afraid something got screwed up by merging in the template update.

@heylf
Copy link
Contributor Author

heylf commented Mar 7, 2024

@grst yeah saw right now that this PR was still hanging nf-core/modules#4839. If its merged then it should be fine.

@grst
Copy link
Member

grst commented Mar 11, 2024

@heylf, if you look at the diff, there's now basically no changes left since I merged in the template update.

@heylf
Copy link
Contributor Author

heylf commented Mar 11, 2024

@grst Yeah its fine to merge

@grst grst enabled auto-merge March 13, 2024 07:07
grst
grst approved these changes Mar 13, 2024
View reviewed changes
Copy link
Member

@grst grst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@grst grst merged commit d554870 into nf-core:dev Mar 13, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@grst grst grst approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@heylf @grst