Changelog automation

[mikemhenry]

Developers certificate of origin

• I certify that this contribution is covered by the MIT License here and the Developer Certificate of Origin at https://developercertificate.org/.

[mikemhenry]

So I only set this up to do the changelog. It can do other things https://regro.github.io/rever-docs/index.html but I wanted to keep it simple for now, but I think we should consider using it to automate our release.

Each time someone makes a PR, they will:

1. Make a copy of TEMPLATE.rst in the news/ folder, for example new_feature.rst
2. Fill out the relevant change log entries

When it is time to make a release, run rever <version> for example rever 1.0.0rc0. This will consolidate all the entries into docs/CHANGELOG.rst.

For example this is what it looks like after running rever 1.0.0rc0

I am not sure where you want to link docs/CHANGELOG.rst on our docs page.

[mikemhenry]

After we merge this in, I will update our wiki for how to do a release.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1562674) 91.89% compared to head (5996129) 90.98%.
Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #728      +/-   ##
==========================================
- Coverage   91.89%   90.98%   -0.92%     
==========================================
  Files         133      133              
  Lines        9650     9650              
==========================================
- Hits         8868     8780      -88     
- Misses        782      870      +88     

Flag	Coverage Δ
fast-tests	90.98% <ø> (-0.92%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[richardjgowers]

@mikemhenry looks good thanks