We would like to create a way of automatically update the `codemeta.json` file when creating a release. This will ease a lot the memory/work of developer, as currently the only way to update the metadata file is by doing it manually.
We would like to create a way of automatically update the `codemeta.json` file when creating a release. This will ease a lot the memory/work of developer, as currently the only way to update the metadata file is by doing it manually.
The v0.1 solution turns around including a pre-hook or a push to `main`/`master` before/after creating the tag/a commit. The problem appears in the moment this branch is protected.
The v0.1 solution turns around including a pre-hook or a push to `main`/`master` before/after creating the tag/a commit. Two problems arise:
- one can't modify the tag once done
Another solution could be to update on the fly the `codemeta.json` file that will be updated into Zenodo, and immediately after push/create a MR to update the metadata file in the git repo. Different solutions are ongoing.
- one can't update the main branch if it's protected (which in many cases).
Another solution could be to update on the fly the `codemeta.json` file that will be updated into Zenodo, and immediately after push/create a MR to update the metadata file in the git repo. Different solutions are ongoing.
