Demo proposal: Automated development pipeline for Chrome extensions #1076
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.
Video demo: Automated development pipeline for Chrome extensions
Members
Andreas Kärrby (karrby@kth.se)
Github: andreaskth
Henrik Kultala (kultala@kth.se)
Github: hengque
Proposal
We would like to create a video demonstrating setup of an automated CI/CD development pipeline for developing and publishing Chrome extensions ("plugins") to the 'extensions' part of Chrome Web Store (and to registered testers of the extension).
A rough list of things we plan to show (level of detail will be adapted to fit given video length):
Sources
https://developer.chrome.com/docs/extensions/mv3/overview/
https://developer.chrome.com/docs/webstore/using_webstore_api/#trustedtesters