👋 @man-shu 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.

The error:

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.66%. Comparing base (087f713) to head (561f63e).
Report is 2 commits behind head on main.

@@           Coverage Diff           @@
##             main    #4854   +/-   ##
=======================================
  Coverage   93.66%   93.66%           
=======================================
  Files         136      136           
  Lines       17147    17147           
  Branches     2962     2962           
=======================================
  Hits        16060    16060           
  Misses        577      577           
  Partials      510      510           

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

• it seems git clone can handle making a new directory if the specified cloning path does not exist. Now I think this happens because we are trying to do things in . and we might not have permissions to create directory there. So now we do everything in ~/

Update on my hypothesis for why the release docs workflow fails

Will merge and test this on my fork see if this goes further.

ok it is failing on my fork for other reasons.

but there is a workflow dispatch on this workflow so we can trigger it manually on the upstream: https://github.com/nilearn/nilearn/actions/runs/12137153863

🤞🏽

get_data failed so I re ran it

ok this is still failing

I think we should try to see if we can modify our regular doc publishing workflow to do the trick