-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
β¨ feat: Automation of the web extension deployment #201
Labels
enhancement
New feature or request
Comments
mauroerta
added a commit
that referenced
this issue
May 27, 2022
12 tasks
mauroerta
added a commit
that referenced
this issue
May 27, 2022
mauroerta
added a commit
that referenced
this issue
May 27, 2022
mauroerta
added a commit
that referenced
this issue
May 27, 2022
mauroerta
added a commit
that referenced
this issue
May 27, 2022
mauroerta
added a commit
that referenced
this issue
May 27, 2022
mauroerta
added a commit
that referenced
this issue
May 28, 2022
mauroerta
added a commit
that referenced
this issue
May 28, 2022
mauroerta
added a commit
that referenced
this issue
May 28, 2022
mauroerta
added a commit
that referenced
this issue
May 28, 2022
mauroerta
added a commit
that referenced
this issue
May 28, 2022
chore(devtool): #201 automate web extension deployment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
π€ Problem
Currently, the deployment of a new version of the browser extension is made completely manually... π
π Solution
Using the Chrome Web Store API it's actually possible to automate this process!
The text was updated successfully, but these errors were encountered: