How should I structure my repo/branches if I'm working on multiple nf-core modules? The speed at which

nf-core/modules

repo moves at (which is a good thing), means the

main

branch of my fork will fall back further and further behind. Is this a problem?

No problem, just regularly update the PR branch (can do that in the github gui).

Thanks Matthias! I'll start doing that. You've seen all my dumb pull requests 😭

Yeah, my approach is never to commit stuff to my forks

main

- always on branches. But every time I start a new branch, before I make it I press 'sync fork'

I sync my main branch from upstream every time I start working on a new feature, and create a new branch

In case something goes wrong,

git reset --hard origin/master

does wonders

I just never work on a fork, and always just work directly on branches on nf-core 🤷

I just never work on a fork, and always just work directly on branches on nf-core 🤷

Wait a sec, I can just make a branch on nf-core?! Ooookay

You could but we don't like it

That's totally fair, that was one reason why I work on my own repo!

For some pipelines like sarek, due to the use of secrets you don't have a choice