ci(PLT-4224): replace secrets.GH_TOKEN with secrets.JENKINS_PAT_TOKEN - #264
Conversation
✅ Security Analysis ResultsGreat news! No security issues found in this pull request. Analysis Summary:
💡 Trigger a new security scan by commenting Security analysis powered by Claude Sonnet 4.6 via pr-auditor | Questions? Contact #dx-team or check out this page |
|
🥷 Code experts: kb-typeform kb-typeform, bobobowis have most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame:
Activity based on git-commit:
Knowledge based on git-blame: ✨ Comment |
jhuliano
left a comment
There was a problem hiding this comment.
LGTM — automated approval for PLT-4224 migration (replace GH_TOKEN with JENKINS_PAT_TOKEN)
Why
We are deprecating the org-level GitHub Actions / Dependabot secret
GH_TOKENand standardizing onJENKINS_PAT_TOKEN.Context (PLT-4224):
GH_TOKENis a legacy org secret name that is easy to confuse with GitHub's built-in default token (secrets.GITHUB_TOKEN/github.token).jenkins-tfservice account PAT, used for CI tasks such as private package installs, Dependabot auth, and other automation that needs a stable org-scoped token.JENKINS_PAT_TOKENas the replacement org secret with clearer ownership and naming. The oldGH_TOKENwill be revoked after org-wide migration is complete.Why this change matters:
JENKINS_PAT_TOKEN→jenkins-tf)GITHUB_TOKENWhat changed
secrets.GH_TOKEN→secrets.JENKINS_PAT_TOKENin:.github/workflows/**dependabot.yml/dependabot.yaml).githuborg repo:reusable-workflows/**,workflow-templates/**templates/*.ymlworkflow templates where applicableGH_TOKEN:andGITHUB_TOKEN:— only the secret reference on the right is updated.What we did not change
secrets.GITHUB_TOKEN/ built-ingithub.token(default GitHub Actions token)ATLANTIS_GH_TOKENor other unrelated secretsgithub_tokenconfigurationTest plan
Rollback
While org
GH_TOKENstill exists, revert this PR to restoresecrets.GH_TOKENif needed.Created by Sourcegraph batch change
muhammad.sayed/plt-4224-gh-token-delivery-experience.