Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

Powered by ReviewNB

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.40%. Comparing base (9b85b2a) to head (d1688bc).
Report is 10 commits behind head on main.

@@           Coverage Diff           @@
##             main     #437   +/-   ##
=======================================
  Coverage   94.40%   94.40%           
=======================================
  Files          31       31           
  Lines        1985     1985           
=======================================
  Hits         1874     1874           
  Misses        111      111           

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

Pre commit checks were failing. Just ran them and it updated the copyright year, see previous commit. It updated 2024 to 2025.

@lucianopaz could I get your input here? We've got 2 issues in the remote checks.

Problem 1

One of them is your https://github.com/lucianopaz/head_of_apache pre commit check. It's already ran this and it changed

- Copyright 2024 The PyMC Labs Developers
+ Copyright 2025 The PyMC Labs Developers

Which seems fine.

But now it seems to want to do

- Copyright 2025 The PyMC Labs Developers
+ Copyright 2025 - 2025 The PyMC Labs Developers

which seems like a bug to me.

Problem 2

The other issue involves the setting up of the remote environment

Copilot is telling me to:

1. Add a step to build the wheel file before the installation step.
2. Ensure the dist directory exists and contains the wheel file.

But thought I'd just check this makes sense before I trust it :)

Thanks for any input you can give

I can answer on the head of apache thing. The people from numfocus said that leaving just the current year on the license header was wrong because it implied that we were forfeiting the license from past years. That's why the format that the hook imposes now is first_year - current_year_or_present. When there's only one year in the license header, it assumes that's the start year for the license and then does first_year - current_year. If you prefer, you can make the license show first_year - present.

If you want, I can change the start years to the year in which CausalPy was first released, and then the license will show 2022-2025

Ah, that makes sense. Sure thing, happy for you to do that :)