chainguard-dev / chainguard-dev/actions
Wolfi-dev OS actions - resource not accessible warning
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 173
- Forks
- 83
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 11
Description
2024-04-10T11:55:40.7937799Z ##[group]Run thollander/actions-comment-pull-request@fabd468d3a1a0b97feee5f6b9e499eab0dd903f6
2024-04-10T11:55:40.7938384Z with:
2024-04-10T11:55:40.7938595Z filePath: diff.log
2024-04-10T11:55:40.7939344Z GITHUB_TOKEN: ***
2024-04-10T11:55:40.7939599Z mode: upsert
2024-04-10T11:55:40.7939838Z create_if_not_exists: true
2024-04-10T11:55:40.7940119Z ##[endgroup]
2024-04-10T11:55:41.0317790Z ##[error]Resource not accessible by integration
2024-04-10T11:55:41.0405868Z ##[group]Run actions/upload-artifact@5d5d22a31266ced268874388b861e4b58bb5c2f3
2024-04-10T11:55:41.0406471Z with:
2024-04-10T11:55:41.0406723Z path: ./packages/x86_64
./packages.log
As mentioned in annotations at https://github.com/wolfi-dev/os/actions/runs/8630712801
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked workflow run and its annotations, focusing on the thollander/actions-comment-pull-request invocation that reports “Resource not accessible by integration.” Compare its permissions and context with the subsequent actions/upload-artifact step; done means the workflow completes without that resource-access warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100