+
Skip to content

Conversation

KyFaSt
Copy link

@KyFaSt KyFaSt commented Jan 22, 2025

Description

Add recommended minimum permissions to README

Motivation and Context

To reduce risk of over-privileged tokens, we are adding recommended permissions to popular GitHub-owned Actions READMEs

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (add or update README or docs)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

To reduce risk of over-privileged tokens, we are adding recommended permissions to popular GitHub-owned Actions READMEs
@KyFaSt KyFaSt requested a review from a team as a code owner January 22, 2025 02:17

# Recommended Permissions

The `actions/cache` workflow relies on an internal authentication pattern and does not use the GITHUB_TOKEN, to reduce risk of over-privileged token, jobs that use `actions/cache` should set permissions to none:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we using this language consistently in other repositories?

Setting permissions to none would likely broke most workflows - should we make it explicitly clear that other actions in your workflow may need more permissions?

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.

3 participants

点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载