ci-publish
FreeSend main to the Chrome Web Store and Firefox Add-ons, by tagging it `store-<version>`.
The English summary is being prepared. Showing the original description.
Start the release of main by hand (the CI, then a GitHub release of its zips), since no push runs it.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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>).
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Send main to the Chrome Web Store and Firefox Add-ons, by tagging it `store-<version>`.
The English summary is being prepared. Showing the original description.