Skip to content

ci: do not start CLA jobs that exit immediately #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rabestro merged 1 commit into from
Sep 14, 2026
Merged

ci: do not start CLA jobs that exit immediately #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/workflows/cla.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,16 @@ permissions:

jobs:
cla-check:
# The script below already returns immediately for bots and for owners,
# members and collaborators — but only after the job has started, and a
# started job is billed a whole minute however fast it exits. Hoisting the
# same test to the job level means it is never started at all. Behaviour is
# unchanged: the check still runs, on GitHub-hosted infrastructure, for the
# external contributors it exists for.
if: >-
!endsWith(github.event.pull_request.user.login, '[bot]') &&
!contains(fromJSON('["OWNER","MEMBER","COLLABORATOR"]'),
github.event.pull_request.author_association)
runs-on: ubuntu-latest
steps:
- name: Harden the runner (audit egress)
Expand Down