We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It turns out that using tag protection doesn't work the way we'd hoped, but we can do the following instead to enforce admin-only publish:
content:write
gh.repos.get_collaborator_permission_level(‘$GITHUB_ACTOR’)[‘permission’]
For the shared PyPI credentials, we can create a bot pypi user per org, and add a scoped release token per repo in the org.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
It turns out that using tag protection doesn't work the way we'd hoped, but we can do the following instead to enforce admin-only publish:
content:write
permissiongh.repos.get_collaborator_permission_level(‘$GITHUB_ACTOR’)[‘permission’]
is “admin”For the shared PyPI credentials, we can create a bot pypi user per org, and add a scoped release token per repo in the org.
The text was updated successfully, but these errors were encountered: