nextcloud / nextcloud/documentation
labeller action seems to have issues with forks
Open
Nobody has claimed this yet.
0. needs triage
bug
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
The configuration file (path: .github/labeler.yml) was not found locally, fetching via the api
Error: HttpError: Resource not accessible by integration - https://docs.github.com/rest/issues/labels#set-labels-for-an-issue
Error: Resource not accessible by integration - https://docs.github.com/rest/issues/labels#set-labels-for-an-issue
didn't look deep into it, encountered here: https://github.com/nextcloud/documentation/actions/runs/33291126664/job/99428317583?pr=15495
related: https://github.com/actions/labeler/issues/814
Contributor guide
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 workflow run linked in the issue and inspect the configuration lookup for .github/labeler.yml, then compare the permission error with actions/labeler issue 814 and the GitHub labels API endpoint. Done means the labeler behavior for fork pull requests is corrected or the limitation and required configuration are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100