Skip to content

CLA: use release-workflows v1.3.0 - #335

Merged
liquidsec merged 2 commits into
devfrom
feat/cla-v1.3.0
Nov 13, 2026
Merged

liquidsec merged 2 commits into
devfrom
feat/cla-v1.3.0

Conversation

@pjhartlieb

Copy link
Copy Markdown
Contributor

Replaces the inline copy of the CLA action with the shared workflow, release-workflows v1.3.0. The check is now named cla / CLAAssistant (was CLAAssistant; required nowhere).

  • Signatures save again, on CLA's bot-only signatures branch. None have saved since 10-27: CLA main refuses the bot's push.
  • Who signs: on a pull request opened by an org member or named bot, other members and bots are exempt; on one opened by anyone else, the opener and every commit author sign, members included.
  • The App token is minted only for pull request events and sign/recheck comments, and only for the CLA repository.
  • Fails for a maintainer to handle, instead of passing, when the commits can't all be read or a commit's author has no GitHub login.

Comments run the workflow on the default branch (stable), which keeps the old copy until the next promotion. Until then, after a contributor signs, a maintainer re-runs the pull request's CLA check ("Re-run all jobs").

Details: blacklanternsecurity/release-workflows#18 and #20.

@liquidsec
liquidsec merged commit c665c5e into dev Nov 13, 2026
20 checks passed
@liquidsec
liquidsec deleted the feat/cla-v1.3.0 branch November 13, 2026 23:04
@liquidsec liquidsec mentioned this pull request Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants