Very carefully delete any branches that are unnecessary (especially ones that have already been merged)

[SPPearce]

There are currently 151 branches in the repo, some of which are not relevant (e.g. they have been created to add data but not deleted at the end of the PR).

[muffato]

I deleted the ones that are stale and are linked to pull requests merged or closed (most often because they were onto master and have been superseded with another one onto the right branch). Still 134 left 😩

[SPPearce]

Well, we have something like 110 pipelines in total including the archived ones, so that doesn't sound too bad

[muffato]

Oh, didn't realise there were that many ! Not too bad indeed. Here is my list of branches with a name that suggests an action could be taken.

revert-* ones branches like revert-417-modules, revert-653-melt, etc. All stale. I'm sure the number refers to a PR/issue number of an nf-core repo.

Two also probably linked to a PR/issue but have apparently no commit of their own ?

• https://github.com/nf-core/test-datasets/tree/1240-bcl_demultiplex-subworkflow
• https://github.com/nf-core/test-datasets/tree/1208-testdata-for-xeniumranger-modules

Two are very small changes that have been forgotten. Maybe they're not needed after all ? Would probably need to check that those branches are not used in any module test

• https://github.com/nf-core/test-datasets/compare/modules...saulpierotti-patch-1
• https://github.com/nf-core/test-datasets/compare/modules...updates_names

There's one for sarek with a capital s:

• https://github.com/nf-core/test-datasets/tree/Sarek
• instead of https://github.com/nf-core/test-datasets/tree/sarek