[llvm] [GitHub] Add basic CI for libclang Python binding unit tests (PR #76784)

Tom Stellard via llvm-commits llvm-commits at lists.llvm.org
Fri Jan 26 21:57:05 PST 2024


================
@@ -0,0 +1,39 @@
+name: Libclang Python Binding Tests
+
+permissions:
+  contents: read
+
+on:
+  workflow_dispatch:
+  push:
----------------
tstellar wrote:

I think for now we need to continue to restrict our workflows to the llvm organization or the llvm/llvm-project repository.  I agree with you, though, that doing this makes testing harder and is inconvenient for forks that actually do want to test.  On the other hand asking all the thousands of forks to manually disable the workflows doesn't seem like it scales well.

I don't know which solution is best, but we have had people complain in the past about unwanted workflows running in their forks.  I'm not sure if they were aware of this option, though.

If we want to change our policy and remove the llvm org and llvm/llvm-project repo restrictions from our workflows, then I think we need an RFC to see how the rest of the community and the fork owners feel about this.

https://github.com/llvm/llvm-project/pull/76784


More information about the llvm-commits mailing list