Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/xeger/webext-circleci-tweaks
Web browser extension to enhance the CircleCI user interface.
https://github.com/xeger/webext-circleci-tweaks
circleci webextension
Last synced: about 1 month ago
JSON representation
Web browser extension to enhance the CircleCI user interface.
- Host: GitHub
- URL: https://github.com/xeger/webext-circleci-tweaks
- Owner: xeger
- License: mit
- Created: 2021-04-02T16:11:38.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2021-09-16T00:29:20.000Z (over 3 years ago)
- Last Synced: 2023-04-01T10:13:06.061Z (over 1 year ago)
- Topics: circleci, webextension
- Language: JavaScript
- Homepage:
- Size: 741 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.md
Awesome Lists containing this project
README
# webext-circleci-tweaks
Web extension for [Chrome](https://chrome.google.com/webstore/detail/circleci-tweaks/ckgcdofchjnpdocejdjmajhnpgnohklf?hl=en&authuser=1) and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/circleci-tweaks/).
## Features
TODO
## Configuration
TODO
## Contributor's Guide
### Publishing By Hand
Edit `source/manifest.json` and bump the version. Commit this and add corresponding git tag; `git push --tags`.
Build the distribution files.
```
npm run build
```
Create the source zip to submit for Firefox security review.
```
zip ./webext-circleci-tweaks-source.zip *.md *.json source/*
```
Create the distributable zip to upload to the Chrome + Firefox developer dashboards.
```
cd distribution
zip ../webext-circleci-tweaks.zip *
```
Upload all the zips!
### Publishing
It's possible to automatically publish to both the Chrome Web Store and Mozilla Addons at once by adding these secrets on GitHub Actions:
1. `CLIENT_ID`, `CLIENT_SECRET`, and `REFRESH_TOKEN` from [Google APIs][link-cws-keys].
2. `WEB_EXT_API_KEY`, and `WEB_EXT_API_SECRET` from [AMO][link-amo-keys].
Also include `EXTENSION_ID` in the secrets ([how to find it](https://stackoverflow.com/a/8946415/288906)) and add Mozilla’s [`gecko.id`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings) to `manifest.json`.
The GitHub Actions workflow will:
1. Build the extension
2. Create a version number based on the current UTC date time, like [`19.6.16`](https://github.com/fregante/daily-version-action) and sets it in the manifest.json
3. Deploy it to both stores
#### Auto-publishing
Thanks to the included [GitHub Action Workflows](.github/workflows), if you set up those secrets in the repo's Settings, the deployment will automatically happen:
- on a schedule, by default [every week](.github/workflows/deploy-automatic.yml) (but only if there are any new commits in the last tag)
- manually, by clicking ["Run workflow"](https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/) in the Actions tab.