Community

[mastoffel]

• fix links
• create gh-action to publish to pypi
• add release docs for maintainers

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.17%. Comparing base (7a4dc72) to head (f821e6b).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #296      +/-   ##
==========================================
- Coverage   94.20%   94.17%   -0.03%     
==========================================
  Files          62       62              
  Lines        3606     3606              
==========================================
- Hits         3397     3396       -1     
- Misses        209      210       +1     

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

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
autoemulate/emulators
gaussian_process.py
Project Total

This report was generated by python-coverage-comment-action

[mastoffel]

@marjanfamili @radka-j . I've added a gh-action workflow to automatically release the package on PyPi when pushing a new version tag as suggested in #287. To make this clear, I added a guide in the documentation (docs/community/release.md). I'm just wondering now whether this should just be under "community" as releasing requires maintainer rights, or whether we should have a seperate maintainer section or so for this. Would do you think?

[marjanfamili]

LGTM

[radka-j]

Looks great! The updated links work for me.

Only thought I had was whether there are any versioning guidelines we follow that we can link to in the release section? There might not be, this stuff is probably always more subjective than anything else.

I think keeping the release docs in the community section as is or adding a new maintainer section are both equally good options so pick whichever you're most comfortable with.

[mastoffel]

Thanks both! @radka-j I added this guide, which I think is simple and intuitive.