https://nf-co.re logo
Join Slack
Powered by
Hey there! I am kind of new here, but would like t...
# tools
a
Hey there! I am kind of new here, but would like to work on one of the "good first issue"s I for myself looked into the Issue #3422: "Behaviour of lint check 
files_unchanged
is different in 3.1.2" Is this still going? Or is someone already contributing on this one?
m
I think we solved this now. but maybe you can double check?
a
When looking into the GitHub Issue there is no PR linked to it, but I can look into the merged PRs
m
i would first try if you can reproduce the error
a
manifest.contributors
is now a required field. Not 100% sure if you’d cause an error by having a 
contributors
section but no 
name
set within them though, so you might want to check that possibility.
One thing to note is I don’t think anyone has assigned the 
good-first-issue
label in nearly a year, so there may well be newer issues which are quite approachable for someone new to the codebase but simply not highlighted as such. In general older issues are in fact probably harder (hence being left unsolved) and the context will quite possibly have changed given a number of releases in the past 12 months, some with significant changes.
👍 1
a
I changed the name parameters in contributors to '' and ran it again. There was no crash when using 
nf-core pipelines lint --dir /tmp/pairgenomealign
So I guess the issue is fixed?
a
It would seem so
a
Then I'll look for other issues to work on. Since this is my first time working with nextflow, finding a good starter issue will be kind of hard, I think
m
what's your background. maybe i can point you to something more up you valley?
a
Not that great actually. Just a simple bioinformatics bsc student And worked a bit on OpenMS. But since that is C++ and this is rather python based, I dont really have a background to talk about
m
no worries, we all started somewhere 🙂 but if you want to work more with nextflow, the tools repo is maybe not the best starting point, because we are providing tooling for the community there and don't write so much actual nextflow code. For that the modules repo might be a better place. especially topic migration (see https://nf-co.re/hackathon-projects/hackathon-march-2026/modules as a primer for that )
a
Thank you very much! But just clearly out of interest; lableing Issues isn't such a thing happening often on GitHub, right? ._.
300+ Issues, just around 50 labled
m
we usually do it before hackathons and it is up to the repo maintainer
ah, you mean on tools. we usually have some labels (i just see 34 without a label)
a
I am talking about the modules Repo
m
ah, okay there we don't label as much, as the issues are more to help keeping track of who does what
s
The issues on 
nf-core/modules
come in a few different forms: • I want a new module (and maybe assigning themselves) • I found a bug / need something fixing • Lists of modules that need changing in some way to ensure no duplication of work, like the ongoing effort to swap to using topics channels • Notes saying that something was broken that was tangentially related to a task at hand, and has never been looked at again 😉
Basically nobody really looks at the issues board too much
Although I do see labels on virtually all of them, except the topic migration sub-issues
Taking a topic migration would be simple and well defined
a
For reference, here is the meta-issue collecting all of the sub-issues related to topics migration and the main instructions: https://github.com/nf-core/modules/issues/9978 We are now in PART 6. You can grab any of the open ones :)
a
I'd probably work on the muscle Module then, migrating it However, I THINK I will start with a proper introduction into nextflow by really doing the tutorials, not just skimming it. MSAs are things we already did in our bachelors, though, so I'd feel comfortable later working on something I already know
👍 2
m
a
Yes, I am already setting everything up for Hello Nextflow ^^, then working myself to Hello nf-core
🎉 2
s
If you need help, then please ask. We do have a channel for the topics migration: #C09LJTQQ3EY
4 Views
Open in Slack
PreviousNext
Powered by