Add deploy workflow

[ColdSauce]

Hi Chrome team! :)

We created a Github action to make it easier to publish extensions to the various web stores programatically.

Thought y'all might find it useful so I added a Github workflow that will run the build step and publish to the Chrome web store on dispatch.

The only thing you would need to create is a SUBMIT_KEYS GitHub repository secret.

This secret is a JSON, with the schema defined here.

Here's a sample key:

{
  "$schema": "https://raw.githubusercontent.com/plasmo-corp/bpp/v1/keys.schema.json",
  "chrome": {
    "zip": "./extension/chrome.zip",
    "clientId": "123",
    "clientSecret": "456",
    "refreshToken": "789",
    "extId": "abcd"
  },
  "firefox": {
    "zip": "./extension/firefox.xpi",
    "apiKey": "123",
    "apiSecret": "abcd",
    "extId": "foobar"
  }
}

You can find instructions on how to get those keys in the schema, or if you use vscode, the schema should provide hint/intelisense when hovering over the json properties. If you need any help in setting up the keys, feel free to @ me.

Otherwise, if this doesn't seem necessary, feel free to close the PR!

(p.s. it shows I commited the dependabot due to a rebase)

[hoch]

Thanks for the PR, but can you clarify a bit more?

make it easier to publish extensions to the various web stores programatically.

Publishing an extension to the store requires an explicit approval. What do you mean by "making it easier"?

[ColdSauce]

When the decision has been made that it's okay to deploy the extension to the Chrome Web Store, our tool automates the process of building the extension, and uploading the zip file to the store via the Chrome Web Store API.

We've built a Github Action giving the ability to deploy via a task runner within Github with one click.

Here's an example from one of our Github repos: In the Actions tab,

We can select the workflow, and then run it for any branch in our repo:

So instead of having to clone the repo, zip things up manually, browse to the web store, upload the zip file, etc we make it possible to deploy to the store with one click.

Anything that occurs before the decision to deploy the extension is made, or after it has been deployed is outside the scope of this tool.

[hoch]

Thanks for the idea! It looks useful. Out team will circle back and discuss when we actually launch the project.

[hoch]

The linked GitHub action is not available anymore and it is unlikely that our team will pursue this option.