Skip to content

[build] GitHub Actions secret cleanup #4855

@arturcic

Description

@arturcic

Intent

Reduce risk and maintenance overhead in GitHub Actions credentials by using least-privilege defaults and reserving high-privilege tokens only for scenarios that truly need them.

Idea in General

This effort standardizes how authentication is handled across build and release automation:

  • Prefer the built-in GitHub token for same-repository operations.
  • Treat non-sensitive toggles as configuration variables, not secrets.
  • Keep personal access tokens only where workflow triggering or cross-repository updates require them.
  • Make the credential model easier to understand, review, and audit over time.

Expected Outcome

A simpler and safer CI/CD credential strategy with clearer ownership of permissions and fewer broad-scope secrets in routine workflow paths.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions