👋 @Remi-Gau Thanks for creating a PR!

Until this PR is ready for review, you can include the [WIP] tag in its title, or leave it as a github draft.

Please make sure it is compliant with our contributing guidelines. In particular, be sure it checks the boxes listed below.

• PR has an interpretable title.
• PR links to Github issue with mention Closes #XXXX (see our documentation on PR structure)
• Code is PEP8-compliant (see our documentation on coding style)
• Changelog or what's new entry in doc/changes/latest.rst (see our documentation on PR structure)

For new features:

• There is at least one unit test per new function / class (see our documentation on testing)
• The new feature is demoed in at least one relevant example.

For bug fixes:

• There is at least one test that would fail under the original bug conditions.

We will review it as quick as possible, feel free to ping us with questions if needed.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.12%. Comparing base (abb80ff) to head (e58a24d).
Report is 49 commits behind head on main.

@@            Coverage Diff             @@
##             main    #4307      +/-   ##
==========================================
+ Coverage   91.85%   92.12%   +0.27%     
==========================================
  Files         144      143       -1     
  Lines       16419    16438      +19     
  Branches     3434     3444      +10     
==========================================
+ Hits        15082    15144      +62     
+ Misses        792      749      -43     
  Partials      545      545              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

For review

Before (current dev doc)

• maskers reports: https://nilearn.github.io/dev/modules/generated_reports/masker_reports_examples.html

After

• maskers reports: https://output.circle-artifacts.com/output/job/2c9fcc23-9f65-4d3a-9154-958b9dcd5876/artifacts/0/dev/modules/generated_reports/masker_reports_examples.html

I like the change.

Given that this is not a bug fix (next release should be mostly bug fixes) I think we can take the time to think about it and possibly find a way to not display them in notebooks.

probably worth refactoring the CSS across reports first

• blocked by report CSS and code refactor #4368