Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not add label(s) to issue #80

Closed
waynexia opened this issue Dec 26, 2023 · 1 comment
Closed

Could not add label(s) to issue #80

waynexia opened this issue Dec 26, 2023 · 1 comment

Comments

@waynexia
Copy link

Example workflow: https://github.com/GreptimeTeam/greptimedb/actions/runs/7327676623/job/19954858878
Config yml: https://github.com/GreptimeTeam/greptimedb/blob/develop/.github/doc-label-config.yml
Workflow file: https://github.com/GreptimeTeam/greptimedb/blob/develop/.github/workflows/doc-label.yml

Error:

Run github/issue-labeler@v3.3
Configuration file (path: .github/doc-label-config.yml) does not exist locally, fetching via the API
Could not add label(s) Doc not needed to issue #3007
Error: AggregateError

Hi, I encountered this issue on trying to use issue-labeler to add labels based on PR description. I guess this is caused by some permission problem, but I don't know the actual reason from the error message. And that token secrets.GITHUB_TOKEN works well on other workflows, example.

And I've tried this config on my forked repo, it also works as expected: waynexia/greptimedb#2

@waynexia
Copy link
Author

The problem is solved. It's because the fork repo cannot access secrets in target repo. Change pull_request to pull_request_target can avoid this: GreptimeTeam/greptimedb#3011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant