Skip to content

fix(ci,ps168): cla.yml uses GH_PERSONAL_ACCESS_TOKEN secret#321

Open
ywatanabe1989 wants to merge 1 commit into
mainfrom
fix/ps168-cla-secret-rename-gh-pat
Open

fix(ci,ps168): cla.yml uses GH_PERSONAL_ACCESS_TOKEN secret#321
ywatanabe1989 wants to merge 1 commit into
mainfrom
fix/ps168-cla-secret-rename-gh-pat

Conversation

@ywatanabe1989

Copy link
Copy Markdown
Owner

Ecosystem-wide rename of the CLA Assistant PAT secret to GH_PERSONAL_ACCESS_TOKEN (GITHUB_* is reserved by GitHub Actions on the secret-name surface). Self-contained — cla.yml + pyproject [tool.scitex_dev.audit] ps168_secret_exceptions. Companion PR scitex-dev #122 adds the ecosystem-wide allowlist; lead has already added the new secret to all 69 active scitex-* repos; the old name will be deleted out-of-band once all 61 sibling PRs merge.

The CLA Assistant workflow's PAT secret is being renamed ecosystem-wide
to `GH_PERSONAL_ACCESS_TOKEN` per operator directive. The new name uses
the GH_ gh-CLI namespace because the natural GITHUB_* prefix is reserved
by GitHub Actions on the secret-name surface.

Two edits:

- .github/workflows/cla.yml: secrets.<old> -> secrets.GH_PERSONAL_ACCESS_TOKEN
- pyproject.toml: [tool.scitex_dev.audit] ps168_secret_exceptions pins
  the exception inline so the audit passes on every scitex-dev version
  (the global allowlist update is on scitex-dev PR #122).
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