-
I've read through the docs for automating the publishing process of extensions. I am using something like this:
I'm wondering if I'm missing something but does a |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Haha yup, you're missing something, but it's my fault - I don't link to the docs for all the options in the store docs. If you run the env:
CHROME_EXTENSION_ID: ${{ secrets.CHROME_EXTENSION_ID }}
CHROME_CLIENT_ID: ${{ secrets.CHROME_CLIENT_ID }}
CHROME_CLIENT_SECRET: ${{ secrets.CHROME_CLIENT_SECRET }}
CHROME_REFRESH_TOKEN: ${{ secrets.CHROME_REFRESH_TOKEN }}
CHROME_SKIP_SUBMIT_REVIEW: true I'll update the docs with a link to all the options, because its just missing 🤦 |
Beta Was this translation helpful? Give feedback.
Haha yup, you're missing something, but it's my fault - I don't link to the docs for all the options in the store docs.
If you run the
wxt submit init
orwxt submit --help
, these commands would have shown you all the options, including the--chrome-skip-submit-review
flag/CHROME_SKIP_SUBMIT_REVIEW
env var.I'll update the docs with a link to all the options, because its just missing 🤦