TobKed commented on pull request #6279:
URL: https://github.com/apache/incubator-doris/pull/6279#issuecomment-1019228207


   Hi @tzssangglass , I am happy to help you.
   If undestrand you question correctly, there is no need for any additional 
configuration.
   GITHUB_TOKEN permissions are set here: 
https://github.com/apache/incubator-doris/blob/c2520c878c3d827e27c32f1dab5e5953a25b52e7/.github/workflows/approve-label.yml#L24
   I am pretty sure if you introduce to APISIX  same changes as in in this PR 
it should work out of the box.
   If you need any help with it or some problems occurs do not hesitate to 
contact me.
   
   **Edit**: I've checked https://github.com/apache/apisix/pull/6136 and I 
think the problem which you relates to there is solved here as well: important 
thing here is that labelling consists of two workflows:
   
   - 
https://github.com/apache/incubator-doris/blob/master/.github/workflows/approve-label-trigger.yml
   - 
https://github.com/apache/incubator-doris/blob/master/.github/workflows/approve-label.yml
   
   where first one just triggers second one. Reason for that is described here: 
[Preventing pwn 
requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
 In your case you may need to adjust permissions 
(https://github.com/apache/incubator-doris/blob/c2520c878c3d827e27c32f1dab5e5953a25b52e7/.github/workflows/approve-label.yml#L24).
 This article may be helpful: [Permissions for the 
GITHUB_TOKEN](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to