We have just registered LibTrixi.jl, which is part of libtrixi, a library for using Trixi.jl from C/C++/Fortran. LibTrixi.jl is located in a subdirectory of the main libtrixi repo. For consistency reasons, we would like to tag the entire repo with the version that is also registered as a Julia package.
For this reason, we have run @JuliaRegistrator register subdir=LibTrixi.jl, but configured TagBot to run for the repository root (otherwise, the created tags would be LibTrixi.jl-v0.1.0 instead of v0.1.0).
However, it seems like TagBot outsmarted us and checked the contents (tree hash) of the LibTrixi.jl directory against the tree hash of the repo root, and refused to tag a new version, see here:
Warning: Tree SHA of commit from registry PR does not match
Warning: No matching commit was found for version v0.1.0 (cf98b69f4adf67976d77e7c93642c763f9288c3b)
No new versions to release
Thus, it seems all our attempts to trick TagBot have failed, thus my questions are whether a) there is a mechanism to achieve what we want (i.e., run TagBot on the subdir but allow to create a tag without a subdir prefix), and if not, whether b) it would be an option to add this feature.
Our only alternative would be, as it seems right now, to run TagBot only on the subdir but then manually add another tag and release, or to use a third-party tool entirely (which I would really like to avoid, since I've come to love the simplicity and robustness of TagBot, as well as its pretty summaries of merged PRs and closed issues).
We have just registered LibTrixi.jl, which is part of libtrixi, a library for using Trixi.jl from C/C++/Fortran. LibTrixi.jl is located in a subdirectory of the main libtrixi repo. For consistency reasons, we would like to tag the entire repo with the version that is also registered as a Julia package.
For this reason, we have run
@JuliaRegistrator register subdir=LibTrixi.jl, but configured TagBot to run for the repository root (otherwise, the created tags would beLibTrixi.jl-v0.1.0instead ofv0.1.0).However, it seems like TagBot outsmarted us and checked the contents (tree hash) of the LibTrixi.jl directory against the tree hash of the repo root, and refused to tag a new version, see here:
Thus, it seems all our attempts to trick TagBot have failed, thus my questions are whether a) there is a mechanism to achieve what we want (i.e., run TagBot on the subdir but allow to create a tag without a subdir prefix), and if not, whether b) it would be an option to add this feature.
Our only alternative would be, as it seems right now, to run TagBot only on the subdir but then manually add another tag and release, or to use a third-party tool entirely (which I would really like to avoid, since I've come to love the simplicity and robustness of TagBot, as well as its pretty summaries of merged PRs and closed issues).
cc @bgeihe