Sign CI for extensions.

[uiolee]

Description

Hi there.
I wrote a script for signing extensions. It depends on Github Action. And requires AMO account API

Motivation

Provides an easier way to install the examples.

Additional details

Procedure

1. Detect whether the manifest changes every time you commit.
2. try to Sign by sign-addon.
3. publish to Github Release.

How to test

1. fork and clone this branch
2. set secrets.
   • WEB_EXT_API_KEY
   • WEB_EXT_API_SECRET
     get api key from https://addons.mozilla.org/zh-CN/developers/addon/api/key/
3. change extensions version.
4. push to main or sign branch

Doubt

Whether the ID should be saved to the repository

if not:

• It takes longer to wait for each signing.
• You will see multiple duplicates of the same extension in your AMO account.
• version can be the same.

Related issues and pull requests

#397

[github-actions]

It looks like this is your first pull request. 🎉 Thank you for your contribution! One of the project maintainers will triage and assign the pull request for review. We appreciate your patience. To safeguard the health of the project, please take a moment to read our code of conduct.

[Rob--W]

The Github actions in this repo are meant to support the maintenance of extension examples. The proposed signing action does not fit in this repository.

[uiolee]

Then maybe we should remove those built version in /build

[Rob--W]

Then maybe we should remove those built version in /build

We probably should. We should check whether anything references it and if not just delete it.

[rebloor]

See Remove built extensions #397.