Skip to content

Try fine grained access tokens for release cut #2798

@mbianchidev

Description

@mbianchidev

Basically we need to remove this warning from the docs:

NOTE / TODO: Look into using fine grained tokens: https://stackoverflow.com/questions/78216547/minimum-permissions-for-a-github-access-token-to-clone-push-and-pull-from-repo. Doing the bare minimum seemed to not work.

And put in place the correct process to use fine grained access token instead of a classic PAT during the execution of a kpromo command, which behind the scenes opens a PR to kubernetes/k8s.io

Should be pretty straightforward to try and document.

EDIT: blocked by github/roadmap#600

/kind documentation
/priority important-longterm
/assign @mbianchidev

Metadata

Metadata

Assignees

Labels

kind/documentationCategorizes issue or PR as related to documentation.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions