nikcio commented on PR #722:
URL: https://github.com/apache/lucenenet/pull/722#issuecomment-1291154924

   I've looked a bit around and it might be possible to get a little of both 
worlds. Using the setting explained here:
   
   
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#controlling-changes-from-forks-to-workflows-in-public-repositories
   
   We should be able to
   1. Prevent first time contributors from running the workflows without 
approval or
   2. Prevent "outsiders" from having workflows run automatically
   
   The 2nd option gives a bit more power but also requires more micromanaging.
   
   Furthermore it's possible to trigger a workflow when labeled so we could add 
a specific label to run tests in draft PRs and then extend the if statement to 
include an "or label x is present". 
   
   It is not possible to add a label to a PR when being an "outsider" like me. 
But this might also help prevent possible abuse and should be quite quick for 
someone with access to add a label should it be required.
   
   
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request


-- 
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]

Reply via email to