Error "Resource not accessible by integration"

[RunningLeon]

Description:
Stale workflow failed when closing issues.

 Error: [#1728] Error when creating a comment: Resource not accessible by integration
  Error: [#1728] Error when adding a label: Resource not accessible by integration

log url: https://github.com/open-mmlab/mmdeploy/actions/runs/4301174276/jobs/7498093123#step:2:522
Action version:
stale v7

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.

Expected behavior:
A description of what you expected to happen.

Actual behavior:
A description of what is actually happening.

[dsame]

Hello @RunningLeon , thanks for your input we are starting to review the reported problem

[dsame]

Hello @RunningLeon

can you please confirm you do not have custom github token for the repository?

From the log is the token does not have issues: write permission

GITHUB_TOKEN Permissions
  Contents: read
  Issues: read
  Metadata: read
  PullRequests: read

despite the proper permissions requested in the workflow file:

permissions:
  contents: write # only for delete-branch option
  issues: write
  pull-requests: write

[RunningLeon]

@dsame Hi, thanks. But the github_token is set to have read/write permission in action settings

[dsame]

Hello @RunningLeon, can you please double check the enterprise to which the repo belongs to

does not have restricted polices:

• In the enterprise account sidebar, click Policies.
• Under " Policies", click Actions.
• Under "Workflow permissions", choose whether you want the GITHUB_TOKEN to have read and write access for all scopes, or just read access

[dsame]

Hello @RunningLeon , this is a gentle remainder the issue is staled waiting for response and to be closed soon due to inactivity.

[dsame]

Hello @RunningLeon , i am closing the issue because of long inactivity, but please feel free to reopen it or create a new one in case problem still exists

[RunningLeon]

@dsame Hi, it appeared that once the pr is merged to the master branch, the permission for GITHUB_TOKEN works fine(with write permission for issues as set in workflow yaml). At PR stage, the permission is not right. But this github procedure is not right for some cases. For instance, we add a workflow that requires GITHUB_TOKEN to have write permission in a PR, but the workflow cannot run due to he permission at PR stage. So we don't know whether the code is good to merge to master branch.

[dsame]

Hello @RunningLeon , thanks for the additional info - it is really helpful and from it i see it is much better to ask this question in runner repo - its team is responsible for the described malfunction.

Do you want me to create the new issue there in behalf of you or you'd prefer to create it yourself?