Webhook cleanup #2267
Description
Capturing context to webhook cleanup actions.
| Hook | Comment | Action |
|---|---|---|
CodeCov related |
With the merger of #2213, no longer needed. |  |
notify.travis-ci.org |
Confirmed by @gavinevans that this is legacy from pre github actions run unittests. | |
houdci.com |
Confirmed by @gavinevans as a passed experiment by a previous member of the team. | |
| metoffice.webhook.office.com/webhookb2 | Unknown purpose. Likely tied to MO office365 and not relevant. Disabling for now to see what happens until the new year. |  |
zenodo.org |
On release, metoppv/improver is archived to Zenodo (CERN), generates a DOI for ease of reference in journal papers. |  |
Background
- @gavinevans on zenodo.org
...every time that there's an improver release, this is automatically archived on Zenodo e.g. https://zenodo.org/records/17953912. This generates a DOI, so we can reference individual releases, if we want. We did use this in the past, so that we could reference the codebase within a scientific paper, although I think more recently we've just referenced the BAMS paper (https://doi.org/10.1175/BAMS-D-21-0273.1), rather than the codebase - @gavinevans
...keep Zenodo, as it still provides others with the ability to reference the improver repo directly, rather than the BAMS paper, which might be appropriate. - @gavinevans