You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add this for this repo as well. However, there is one complication: I have used the model tag as the container tag (I.e. stemmus_scope-grpc4bmi:1.5.0 uses the stemmus_scope:1.5.0 container. The workflow uses the repository's tag/release version, which would be stemmus_scope-grpc4bmi:0.4.0.
The text was updated successfully, but these errors were encountered:
With actions/github-script , it is possible to fetch the release tag from the other repository, see some related examples here. However, stemmus_scope-grpc4bmi:0.4.0 is fine. The version of the model e.g. 1.6.1 is specified in the Dockerfile. Since Docker installs latest pystemmusscope, it would be better if the tag aligns with the pystemmusscope release, rather than stemmus_scope itself.
In STEMMUS_SCOPE a new docker image is built and pushed by Github Actions upon a new release.
We should add this for this repo as well. However, there is one complication: I have used the model tag as the container tag (I.e.
stemmus_scope-grpc4bmi:1.5.0
uses thestemmus_scope:1.5.0
container. The workflow uses the repository's tag/release version, which would bestemmus_scope-grpc4bmi:0.4.0
.The text was updated successfully, but these errors were encountered: