Getting started not working
- 主要言語
- JavaScript
- スター
- 167
- フォーク
- 17
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
### Describe the Issue
I'm trying this action in an empty repository and I'm not able to make it working. It says something about missing permissions but it's not specifying which one is missing.
I put the attached workflow in main branch, then I opened a pull request and commented it with
```
.ping | LOG_LEVEL=debug,CPU_CORES=4
```
### Action Configuration
```yaml
name: "command demo"
# the workflow to execute on is comments that are newly created
on:
issue_comment:
types: [ created ]
# permissions needed for reacting to IssueOps commands on issues and PRs
permissions:
pull-requests: write
issues: write
checks: read
jobs:
demo:
runs-on: ubuntu-latest
steps:
# execute IssueOps command logic, hooray!
# this will be used to "gate" all future steps below
- uses: github/command@v1.2.2
id: ping
with:
command: ".ping"
# run your custom logic for your project here - example seen below
# conditionally run some logic here
- name: ping command
if: ${{ steps.ping.outputs.continue == 'true' }}
run: echo 'Got comment in PR \#${{ steps.ping.outputs.issue_number }} with params ${{ steps.ping.outputs.params }}'
```
### Relevant Actions Log Output
```
Run github/command@v1.2.2
##[debug]checking if the context of 'issue_comment' is valid
🧮 detected parameters in command: LOG_LEVEL=debug,CPU_CORES=4
##[debug]raw allowlist value: false
##[debug]no allowlist provided, all users are allowed
Error: GraphqlResponseError: Request failed due to following response errors:
- Resource not accessible by integration
at /home/runner/work/_actions/github/command/v1.2.2/node_modules/@octokit/graphql/dist-node/index.js:113:1
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at prechecks (/home/runner/work/_actions/github/command/v1.2.2/src/functions/prechecks.js:129:1)
at run (/home/runner/work/_actions/github/command/v1.2.2/src/main.js:78:1)
Error: Request failed due to following response errors:
- Resource not accessible by integration
```
### Extra Information
It would be very useful if the action uses some `core.debug` calls in its codebase to better track issues like this one. At the moment even with debug mode there is no output from the action itself.
コントリビューションガイド
調査の方向性
提供された GitHub Actions workflow と comment コマンドで失敗を再現し、その後、アクションログに表示される src/functions/prechecks.js と src/main.js を調べます。prechecks リクエストが報告された権限エラーをどのように処理しているか、またデバッグ出力がどこで出力されるかを確認します。不足している権限を特定でき、アクションが有用なデバッグの詳細を提供すれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github-actions, javascript
- 領域
- ci-cd, devops
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100