Fix UserWarning always being printed

[thomasaarholt]

I noticed that #5268 introduced a small bug that always printed a warning. Now fixed. (@michaelosthege)
I'd be happy to run linting, but the linting/style checks link below from the PR template takes me to a blank page?

Depending on what your PR does, here are a few things you might want to address in the description:

• what are the (breaking) changes that this PR makes?
• important background, or details about the implementation
• are the changes—especially new features—covered by tests and docstrings?
• linting/style checks have been run
• consider adding/updating relevant example notebooks
• right before it's ready to merge, mention the PR in the RELEASE-NOTES.md

[michaelosthege]

Thanks!
We had the instructions on a wiki page. Can't find it right now either 🤔
Essentially:

pip install pre-commit

# To run it automatically on every commit
pre-commit install

# Or to run it manually 
pre-commit run --all

The pre-commit was satisfied with your changes.

[ricardoV94]

Thanks!
We had the instructions on a wiki page. Can't find it right now either 🤔
Essentially:

pip install pre-commit

# To run it automatically on every commit
pre-commit install

# Or to run it manually 
pre-commit run --all

The pre-commit was satisfied with your changes.

The link still has pymc3, the new wiki page uses pymc and directs to the docs. We have to update the new issue template

https://github.com/pymc-devs/pymc/wiki/Python-Code-Style

[codecov]

Codecov Report

Merging #5286 (5aa1c0b) into main (aaea02a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #5286   +/-   ##
=======================================
  Coverage   78.97%   78.97%           
=======================================
  Files          87       87           
  Lines       14351    14352    +1     
=======================================
+ Hits        11334    11335    +1     
  Misses       3017     3017           

Impacted Files	Coverage Δ
pymc/backends/arviz.py	89.16% <100.00%> (+0.04%)	⬆️

[thomasaarholt]

...what is going on with coverage? 😅

[michaelosthege]

...what is going on with coverage? 😅

Our count of finished jobs needed before the first coverage estimate is posted is not correct.
It is set to post a coverage update before all jobs are done. That's because if the count is too high it would never get posted. Not sure, but probably this could be reconfigured to post it exactly when all jobs are done.

The codecov comment should update itself as more jobs complete. There is still some noise in the final result though.

[OriolAbril]

I created a placeholder page for the old name so links continue to work, but we also moved everything to the documentation and shpuld default to that unless there is a compelling reason to use wikis. I updated the wiki but it seems it was renamed right before these changes so the I updated a page where no link was pointing to

All those devdoc style pages should use links to latest (instead of stable or specific versions) and will then be automatically updated with every commit