Send main to the Chrome Web Store and Firefox Add-ons, by tagging it `store-<version>`.
中文简介正在准备中。当前显示原文说明。
Start the release of main by hand (the CI, then a GitHub release of its zips), since no push runs it.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
No push runs the CI, to spare the Actions minutes. This starts the Release
workflow on main: it runs the CI (checks, packages, end-to-end and Firefox
tests), then makes a GitHub release of main's zips. It doesn't reach the
stores: that's /ci-publish. Arguments: $ARGUMENTS; refuse any.
Pass gh the origin repository (--repo <owner>/<repo>, from git remote get-url origin): the checkout has more than one remote.
git fetch origin --tags, then compare origin/main with the local main. If local work
isn't on origin/main yet, say so and stop: don't push for the user.v=$(node scripts/version.ts --ref origin/main): the version it gets.gh workflow run release.yml --ref main. Then find the run it
made (gh run list --workflow release.yml --branch main --event workflow_dispatch --limit 1 --json databaseId,url,status; it may take a
few seconds to appear, so retry briefly) and give its URL and v.Don't wait for the run to finish unless asked: its results are looked at
afterwards (gh run view <id>, gh run watch <id>).
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Send main to the Chrome Web Store and Firefox Add-ons, by tagging it `store-<version>`.
中文简介正在准备中。当前显示原文说明。