Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Happy Hacktoberfest!
I've created a GitHub workflow for your repository that uses https://github.com/PlasmoHQ/bpp to automatically publish your extension to the Chrome Web Store whenever you initiate a dispatch from the actions tab. After you've published a tagged GitHub release, you can input that tag into this workflow, and it will fetch the release asset and send it straight to the CWS.
All that you as a maintainer will need to do is create a new GitHub secret called
SUBMIT_KEYS
, which will be a JSON object with your chrome web store API keys. The JSON schema is defined here.There are instructions on how to get the CWS keys in the JSON schema, or if you use vscode, the schema should provide hint/intelisense when hovering over the JSON properties. Generating a CWS clientId/refreshToken should take no more than 10-15min. If you need any help in setting up the keys, feel free to ping me! Otherwise if this doesn't seem necessary, feel free to close the PR. Cheers!