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

Nfcore demo #155

Merged
merged 2 commits into from
Jul 22, 2024
Merged

Nfcore demo #155

merged 2 commits into from
Jul 22, 2024

Conversation

ggrimes
Copy link
Collaborator

@ggrimes ggrimes commented Jul 22, 2024

updated episode 12 nf-core including using new nf-core/demo pipleine

change hlatyping to nf-core/demo pipeline
updated to latest nf-core tools and rnaseq release
Copy link

github-actions bot commented Jul 22, 2024

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/workflows-nextflow/compare/md-outputs..md-outputs-PR-155

The following changes were observed in the rendered markdown documents:

 12-nfcore.md | 375 +++++++++++++++++++++++++++++++----------------------------
 md5sum.txt   |   2 +-
 2 files changed, 196 insertions(+), 181 deletions(-)
What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2024-07-22 14:10:04 +0000

github-actions bot pushed a commit that referenced this pull request Jul 22, 2024
@ggrimes ggrimes merged commit 711ec43 into main Jul 22, 2024
3 checks passed
@ggrimes ggrimes deleted the nfcore-demo branch July 22, 2024 15:26
github-actions bot pushed a commit that referenced this pull request Jul 22, 2024
Auto-generated via {sandpaper}
Source  : 711ec43
Branch  : main
Author  : Graeme Grimes <graeme.grimes@ed.ac.uk>
Time    : 2024-07-22 15:26:23 +0000
Message : Merge pull request #155 from carpentries-incubator/nfcore-demo

Nfcore demo
github-actions bot pushed a commit that referenced this pull request Jul 22, 2024
Auto-generated via {sandpaper}
Source  : 6fbfe5a
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2024-07-22 15:27:06 +0000
Message : markdown source builds

Auto-generated via {sandpaper}
Source  : 711ec43
Branch  : main
Author  : Graeme Grimes <graeme.grimes@ed.ac.uk>
Time    : 2024-07-22 15:26:23 +0000
Message : Merge pull request #155 from carpentries-incubator/nfcore-demo

Nfcore demo
github-actions bot pushed a commit that referenced this pull request Jul 23, 2024
Auto-generated via {sandpaper}
Source  : 6fbfe5a
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2024-07-22 15:27:06 +0000
Message : markdown source builds

Auto-generated via {sandpaper}
Source  : 711ec43
Branch  : main
Author  : Graeme Grimes <graeme.grimes@ed.ac.uk>
Time    : 2024-07-22 15:26:23 +0000
Message : Merge pull request #155 from carpentries-incubator/nfcore-demo

Nfcore demo
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.

None yet

1 participant