Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automatically build and store compiled extensions #24

Open
patcon opened this issue May 5, 2014 · 3 comments
Open

Automatically build and store compiled extensions #24

patcon opened this issue May 5, 2014 · 3 comments

Comments

@patcon
Copy link
Contributor

patcon commented May 5, 2014

We should be able to do this using travis. If we can't publish the chrome/firefox store, then at the very least we can use the release api to create a release and upload the proper files to github:
https://developer.github.com/v3/repos/releases/#upload-a-release-asset
@patcon patcon changed the title Automatically build and deploy extensions to market Automatically build and store compiled extensions May 5, 2014
@patcon
Copy link
Contributor Author

patcon commented May 9, 2014

https://developer.chrome.com/webstore/using_webstore_api

@patcon
Copy link
Contributor Author

patcon commented May 9, 2014

Undocumented mozilla addon market API:
https://github.com/andymckay/amo-oauth/blob/master/src/amo.py#L224

@patcon
Copy link
Contributor Author

patcon commented May 14, 2014

Allowing multiple users to manage chrome extensions:
https://support.google.com/chrome_webstore/answer/3052863

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@patcon