The QuPath javadocs, however we currently manually trigger builds which means sometimes (e.g., now) we may forget to rebuild the javadocs for a new version.
Triggering the build from this repo on every new release would be much better. The simplest approach would be to check out the javadoc repo and push a tag, although this would require a GH token with cross-repo permissions.
It would be cleaner/better to trigger a specific workflow.
The QuPath javadocs, however we currently manually trigger builds which means sometimes (e.g., now) we may forget to rebuild the javadocs for a new version.
Triggering the build from this repo on every new release would be much better. The simplest approach would be to check out the javadoc repo and push a tag, although this would require a GH token with cross-repo permissions.
It would be cleaner/better to trigger a specific workflow.