Why
Deploys are a headache whenever working on a complex MediaWiki gadget that is based on GitHub. Anything we can do to simplify deploys is good. Simple deploys mean the onwiki gadget is less likely to get out of sync, and it means that merged patches can be deployed fast, easily, and with a minimum amount of specialized knowledge.
What
add this gadget to https://gadget-deploy.toolforge.org/, which is a three-click gadget GitHub-to-wiki deploy tool for interface administrators.
This can be done by following the directions at https://github.com/wikimedia-gadgets/gadget-deploy?tab=readme-ov-file#how-to-configure-a-gadget-for-deployment. Copying from those directions...
Why
Deploys are a headache whenever working on a complex MediaWiki gadget that is based on GitHub. Anything we can do to simplify deploys is good. Simple deploys mean the onwiki gadget is less likely to get out of sync, and it means that merged patches can be deployed fast, easily, and with a minimum amount of specialized knowledge.
What
add this gadget to https://gadget-deploy.toolforge.org/, which is a three-click gadget GitHub-to-wiki deploy tool for interface administrators.
This can be done by following the directions at https://github.com/wikimedia-gadgets/gadget-deploy?tab=readme-ov-file#how-to-configure-a-gadget-for-deployment. Copying from those directions...
npm run deploy). Sounds like we just need to modify it to acceptsiteandaccessTokenfrom a credentials file.