diff options
| author | Dmytro Meleshko <dmytro.meleshko@gmail.com> | 2026-07-13 15:59:31 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-07-13 09:59:31 -0400 |
| commit | e18820007f00541cb95b7ac188666486aaa0a8d9 (patch) | |
| tree | 5485a63edeb577494d493407eed44d5aa828bcbc /runtime/lua/vim/provider/python.lua | |
| parent | 1665b992b7bd34f5130a37a973b292e580adc381 (diff) | |
| download | rneovim-e18820007f00541cb95b7ac188666486aaa0a8d9.tar.gz rneovim-e18820007f00541cb95b7ac188666486aaa0a8d9.tar.bz2 rneovim-e18820007f00541cb95b7ac188666486aaa0a8d9.zip | |
ci: avoid running Coverity in forks #40718
Problem:
If you have this repo forked, the workflow for Coverity Scan creates a lot of
spammy emails about that workflow failing.
Solution:
Check for the presence of `COVERITY_SCAN_TOKEN` and `COVERITY_SCAN_EMAIL` at the
very start of `.github/workflows/coverity.yml`, skip the rest of the workflow if
they are absent. Unfortunately, Github Actions don't offer a straightforward way
of doing that, so using [this workaround](https://github.com/orgs/community/discussions/25280)).
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions