Closed gentlementlegen closed 2 months ago
I think we need to fix the problem with the several notifications caused per release with release-please
It's a problem on the other repos. Otherwise this proposal is fine.
release-please
is important to tag our releases and be able to revert or use specific versions. The main problem I think is that we use develop
as the main branch, when the main branch should also be the one we release on. I do not know if these notifications can be filtered out.
# Issue was not closed as completed. Skipping.
@gentlementlegen i think this is a missed opportunity to make a config page with GitHub login.
Imagine being able to configure your installed instances' ubiquibot-configs with a GUI.
Even better if there was a wizard built in to install a plugin (this is an urgent matter because I never know how to install them, but I do know how to tweak a yml file)
Seems a lot more useful than just a version number.
I suppose we can display the version number on the GUI as well.
Sounds cool. However I believe we should also cover the Action plug-in ones that don't serve a page. I thought it might be easier to have a page where all of them are available.
# Issue was not closed as completed. Skipping.
The page should be in the kernel then, and generated dynamically based on the config.
When the url is served through a
GET
(currently deployed at https://ubiquibot-worker.ubq.workers.dev/) the page just says the headers are incorrect. It might be more useful to get served aJSON
with the current package version, and eventually the corresponding commit, which would help to know what is the current deployed version without needed to access the Cloudflare dashboard. We should also add therelease-please
action to ensure versioning, because I believe it is currently done manually.