What are the minimum requirements for GH_TOKEN

[protoEvangelion]

When generating a GitHub token, what are the minimum scopes required?

I know the docs say "push access", but I am wondering specifically which boxes to check ha 😄

[gr2m]

public_repo if the repository is public, otherwise public. You don’t need the checks for *:repo_hook. Could you maybe send a PR to update the README to make that more clear?

[gr2m]

You can also add links to create a token directly:

• for a private repository: https://github.com/settings/tokens/new?scopes=repo
• for a public repository: https://github.com/settings/tokens/new?scopes=public_repo

[protoEvangelion]

Absolutely 😄 Thanks for the quick response! Will additional permissions be required for the git plugin?

[gr2m]

I don’t think so, I wouldn’t know for what :)

[protoEvangelion]

Sounds good. Does it need to be updated anywhere else besides the readme?

[gr2m]

I don’t think so

[semantic-release-bot]

🎉 This issue has been resolved in version 5.2.7 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[semantic-release-bot]

🎉 This issue has been resolved in version 5.4.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[semantic-release-bot]

🎉 This issue has been resolved in version 5.5.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[semantic-release-bot]

🎉 This issue has been resolved in version 5.6.0-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[semantic-release-bot]

🎉 This issue has been resolved in version 6.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀