在 GitHub Actions 中,我正在测试该actions-ecosystem/action-create-issue操作。
此操作会创建一个自动 github 问题。
但操作崩溃了,我不断收到此错误:
触发此错误(并可用于重现该错误)的工作流程 yaml 文件是以下代码:
name: Deploy to foo
on:
push:
branches: [develop]
jobs:
deploy-to-staging:
name: Deploy to Staging
permissions:
contents: 'read'
id-token: 'write'
runs-on: ubuntu-latest
steps:
- name: Create deploy issue
uses: actions-ecosystem/action-create-issue@v1
with:
github_token: ${{ secrets.github_token }}
title: Hello World
body: |
## Deployed to Staging Server
- [ ] Task-1
- [ ] Task-2
labels: |
deploy
staging
Run Code Online (Sandbox Code Playgroud)
从网上的大量搜索中我找不到答案,大多数资源都将此错误与 github 令牌相关联。
在我的试验和错误过程中,我注意到注释掉整个permissions:属性修复了错误,并创建了一个自动 GitHub 问题,但我确实需要这些权限来在工作流程中执行其他操作,因此删除该permissions:属性对我来说不是一个解决方案。
研究 GitHub 文档时,我发现有一个名为 的特殊权限密钥issues,当我将其添加到permissions:具有其值的属性时write,解决了该错误。
修复的代码是:
name: Deploy to foo
on:
push:
branches: [develop]
jobs:
deploy-to-staging:
name: Deploy to Staging
permissions:
contents: 'read'
id-token: 'write'
issues: 'write' #__This fixed the HttpError: Resource not accessible by integration
runs-on: ubuntu-latest
steps:
- name: Create deploy issue
uses: actions-ecosystem/action-create-issue@v1
with:
github_token: ${{ secrets.github_token }}
title: Hello World
body: |
## Deployed to Staging Server
- [ ] Task-1
- [ ] Task-2
labels: |
deploy
staging
Run Code Online (Sandbox Code Playgroud)
我用于研究的 gitHub 文档是:
GitHub Actions: Control requests for GITHUB_TOKEN
| 归档时间: |
|
| 查看次数: |
6856 次 |
| 最近记录: |