Skip to content

chore(compliance): archive legacy license-cla-check.yml - #60

Open
aabusair wants to merge 1 commit into
mainfrom
chore/archive-license-cla-check
Open

chore(compliance): archive legacy license-cla-check.yml#60
aabusair wants to merge 1 commit into
mainfrom
chore/archive-license-cla-check

Conversation

@aabusair

Copy link
Copy Markdown
Contributor

Moves license-cla-check.yml into workflows/old/, which disables it (GitHub only scans .github/workflows/*.yml directly, not subdirectories).

Confirmed dead before archiving:

  • Only exists in vmware/.github (org-wide code search returned 1 file) — its pull_request_target/issue_comment/pull_request triggers only ever fired on PRs against this repo, never any other repo in the org.
  • Its cla-gate job (contributor-assistant/github-action, a separate CLA mechanism from the current policy_selector.py system, with its own document and signature store) is not referenced by any of the org's 4 Rulesets (active, evaluate, or disabled) — nothing requires it.
  • Its own signature store path (signatures/version1/vmware/.github/cla.json) has never existed in this repo's git history — nobody has ever successfully signed through it.
  • On a real recent PR (fix(compliance): remove duplicate PR-trigger from cla_sweeper.yml #59), cla-gate returned "failure" for an org member that the current system correctly bypassed — direct evidence it's stale, not just unused.
  • The bundled license-check job (REUSE linter) only ever ran against this same single repo with no evidence of active reliance, so it's retired alongside cla-gate rather than split out.

Moves license-cla-check.yml into workflows/old/, which disables it (GitHub
only scans .github/workflows/*.yml directly, not subdirectories).

Confirmed dead before archiving:
- Only exists in vmware/.github (org-wide code search returned 1 file) —
  its pull_request_target/issue_comment/pull_request triggers only ever
  fired on PRs against this repo, never any other repo in the org.
- Its cla-gate job (contributor-assistant/github-action, a separate CLA
  mechanism from the current policy_selector.py system, with its own
  document and signature store) is not referenced by any of the org's 4
  Rulesets (active, evaluate, or disabled) — nothing requires it.
- Its own signature store path (signatures/version1/vmware/.github/cla.json)
  has never existed in this repo's git history — nobody has ever
  successfully signed through it.
- On a real recent PR (#59), cla-gate returned "failure" for an org member
  that the current system correctly bypassed — direct evidence it's stale,
  not just unused.
- The bundled license-check job (REUSE linter) only ever ran against this
  same single repo with no evidence of active reliance, so it's retired
  alongside cla-gate rather than split out.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


Amr AbuSair seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

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.

1 participant