<!here> based on some feedback from a paper review for #CE9MS66BS I'm looking into clean up the badges 'forest' (as @mashehu called it) What do you think about this before/after: • I've tried to remove stuff I didn't feel was relevant (duplicate unit test, social media), and collapse into relevant categories (note mag has 3 extra non-standard badges on the bottom line after Zenodo) • Iv'e added a badge to access to the documentation • Renamed some (e.g. the AWS megatest outputs, singularity to apptainer etc.) Any thoughts in the thread below pretty please 🙏

I love it!

I would group things differently

Hit me

For me it should be: L1: Version (NXF, nf-core, Zenodo, citations) L2: Reproducibility (run with, launch with, develop with + CI) L3: Docs (Read doc, see results, slack + other links)

What about hte linting/nf-test stuff?

for me it goes with Reproducibility, in CI

So like this: (note this is missing a couple as they don't get locally rendered, e.g. Zenodo, conda, slack)

I would personnaly order them by decreasing length 😅 But this already look quite better !

So like in my original version/

Yes, but with the information grouping like Maxime proposed.

OK but that is mutually exclusive 😉

run nf-test "passing"

and

unit tests "nf-test"

seem to be redundant or could be renamed and combined.

I have removed the second one?

ah, sorry was confused which one is current.

The former I can't rename because it comes from the test itself (it's the github automatic ones)

we can (and should) rename the job name

That can be a separate PR (the badge should update automagically I berlieve)

yes, find maxime's a bit clearer, but would do VERSIONS and CITATIONS DOCUMENTATION and LAUNCH + DEVELOP EXECUTION and REPRODUCIBILITY + CI

OK, let me finish something and I'll model that, if Matthias' tweaked version of yours is OK @Maxime Garcia?

yes! also looks nicely balanced (but i guess that is also a bit due to your extra badges). btw. I thought this all started because you wanted to add links to usage and output docs

I could also put output docs, but I think the example results are sort of better for that

Fine with me

Looks good!!

@mashehu updated: https://github.com/nf-core/tools/pull/4288 one of the tests fail because I guess the README string for version bump has changed (I added jijer tags around), but I'm not sure how to escaepe those... in the

test_bump_version.py

file...