英文:
Which GitHub Fine grained access permissions are needed to upload a release to a different repository?
问题
我正在管理一个GitHub组织，其中有多个仓库在发布标签上运行操作以生成仓库的发布。
我已经开始修改操作，将发布上传到一个公共的发布仓库，以便将它们都放在一个地方，使用ncipollo/release-action GitHub操作，并使用具有“repo”权限的基本令牌进行上传。
我想开始使用更精细的权限，但还没有弄清楚需要哪些权限。已经尝试了：
- 读取元数据的访问权限
- 部署的读取和写入访问权限
但都失败了。
有人知道应该使用哪些正确的权限吗？谢谢。
附注：所有仓库都是私有的。
尝试使用“读取和写入部署的访问权限”，但上传失败。
英文:
I'm managing a GitHub organisation, with multiple repositories running actions on release tags that generate a release for the repo.
I've started modifying the actions to upload the releases to a common Release repo to keep them all in one place, with the ncipollo/release-action github action, using a Basic token with the "repo" permission to upload.
I like to start using fine grained permissions instead but haven't been able to figure out the permissions needed. Have tried with:
- Read access to metadata
- Read and Write access to deployments
but that fails.
Anyone know the correct permissions to use? Thanks.
nb. All repositories are private
Tried using the "Read and Write access to deployments" permission, but the upload fails.
答案1
得分: 3
我已解决了发布后不久的问题...
正确的权限是“Contents”，它包括“仓库内容、提交、分支、下载、发布和合并”。
英文:
And of course, I sorted out the issue shortly after posting...
The correct permission to use is "Contents" which covers "Repository contents, commits, branches, downloads, releases, and merges."
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论