mik-laj commented on a change in pull request #31104:
URL: https://github.com/apache/spark/pull/31104#discussion_r554500912



##########
File path: .github/workflows/build_and_test_workflow_run.yml
##########
@@ -0,0 +1,25 @@
+name: Cancelling Duplicates
+on:
+  workflow_run:
+    workflows: 
+      - 'Build and test'
+    types: ['requested']
+
+jobs:
+  cancel-duplicate-workflow-runs:
+    name: "Cancel duplicate workflow runs"
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        name: checkout potiuk/cancel-workflow-runs
+        with:
+          repository: potiuk/cancel-workflow-runs
+          path: ./build/.actions/potiuk/cancel-workflow-runs
+          ref: 953e057dc81d3458935a18d1184c386b0f6b5738 # @master
+          fetch-depth: 1
+      - uses: ./build/.actions/potiuk/cancel-workflow-runs

Review comment:
       Apache INFRA has no possibility of limiting the use of fluent 
references(v2, master, etc) and the rules for using actions are just being 
established. The new policy was only introduced a week or two ago due to one 
security incident, and now the INFRA team is watching how users use custom 
actions and what actions they use. We may try to add these actions to the 
whitelist, but there is little chance of that yet.  For now, INFRA is a bit 
heavy with discussions about other Github Action limitations. See: 
https://lists.apache.org/thread.html/r5303eec41cc1dfc51c15dbe44770e37369330f9644ef09813f649120%40%3Cbuilds.apache.org%3E
 This change is intended to help us fix/mitigate this issue.
   
   In the case of Apache Airflow, we decided to fork this action to apache/ 
(See: https://github.com/apache/airflow-cancel-workflow-runs), but now we 
consider migrations to use submodules (See: 
https://github.com/apache/airflow/issues/13513).
   
   
   




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

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