Create sub-issues for plink module topic channel migrations#10441
Closed
Create sub-issues for plink module topic channel migrations#10441
Conversation
Copilot
AI
changed the title
[WIP] Add sub-issues for Plink functionalities
Create sub-issues for plink module topic channel migrations
Mar 11, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
13 plink submodules need to be migrated to use Nextflow topic channels for version outputs, as part of the broader nf-core modules topic channel adoption effort tracked in #10439.
This PR creates individual sub-issues for each plink module to enable parallel contribution by hackathon participants:
plink/bcfplink/epistasisplink/excludeplink/extractplink/fastepistasisplink/genomeplink/gwasplink/hweplink/indepplink/indeppairwiseplink/ldplink/recodeplink/vcfEach sub-issue references #10439 and describes the required changes: replacing
path "versions.yml", emit: versionswith a topic channel tuple output, updatingmeta.yml, and regenerating test snapshots per the migration guide.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://api.github.com/graphql/usr/bin/gh gh auth status(http block)https://api.github.com/repos/nf-core/modules/issues/10439/usr/bin/curl curl -s -H Authorization: token ****** -H Accept: application/vnd.github.v3+json REDACTED(http block)https://api.github.com/user/usr/bin/gh gh api user(http block)nf-co.re/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.