fregante

Tsk, we can't even agree on **tabs-vs-spaces,** let alone every other single law that would be needed.

He's not working for free, he's working free. Plus at some point he can turn all of these stars into a resume.

I see your point but `cash` is a `node`/ES6 tool, it's built for who already has node installed. Read that as > No ugly DLLs (other than node's, which you...

It's possible and it looks great! https://docs.github.com/en/rest/reference/repos#create-a-deployment-status But this might require a bit of code. I'm considering writing an action

https://github.com/fregante/compact-github-deployment-action

Ah sorry about that. It seemed to work after I made it private, but it guess it stopped. The action wasn’t working as well as intended and I had to...

Undone in 9b1f180

It looks like GitHub added native support for this via `jobs.*.environment` property. See: - https://github.com/refined-github/github-url-detection/deployments/activity_log?environment=github-pages - https://github.com/refined-github/github-url-detection/blob/b93c1f18d7307f72943a95094f4c12127f3ca8c3/.github/workflows/demo.yml#L33-L35 That key likely creates a deployment and keeps track of it as part...

The one that makes the most sense so far is a solution originally posted by @Stvad in https://github.com/fregante/browser-extension-template/issues/75#issuecomment-1124540086 > - create 2 manifests (under `/mv2/manifest.json` and `/mv3/manifest.json`) > - Update...

Alternatively, the extension can be changed to use Manifest v2 after the build runs, originally posted in https://github.com/fregante/browser-extension-template/issues/55#issuecomment-1109165720 > 1. Run `npm run build` > 2. In the `distribution/manifest.json` file,...