Paul Meinhardt

Looks like signing with `web-ext` now works – cf. https://github.com/bitcrowd/tickety-tick/pull/249#issuecomment-652050512. Note: I only tried for unlisted versions so far. ``` yarn build:firefox && WEB_EXT_API_KEY=xxx WEB_EXT_API_SECRET=xxx yarn sign yarn run v1.22.17...

I branched off of `master` and the `master` branch is red, which is probably what causes the build for this PR to fail. 🚥 I could rebase onto the last...

Looks like this is only failing because the `master` branch is "red". How do you suggest to proceed in this case?

> Went for a two step process now @pmeinhardt, in order to align with other bitcrowd open source projects and to not limit releasing to admins only […] > >...

@stickyhands: In this case, the property in question was a UUID and we decided to introduce a special one - `"00000000-0000-0000-0000-000000000000"` - to indicate that the reference should be nulled....

I see the same issue Neovim 0.9.5. This worked for me – as a workaround for setting custom sign symbols: ```vim sign define DiagnosticSignError text=┃ texthl=DiagnosticSignError sign define DiagnosticSignWarn text=┃...

And after some digging… found out you can also set this: ```vim let g:ale_use_neovim_diagnostics_api = 0 ``` It looks as if ALE will set signs via [diagnostics](https://neovim.io/doc/user/diagnostic.html) on Neovim, but...

I guess it depends on which you prefer: 1. Handling issues via diagnostics on Neovim: - In this case customize the `DiagnosticSign*` definitions (see my [first comment](https://github.com/dense-analysis/ale/issues/4777#issuecomment-2118848178)) - This should...