GH-48142: [CI] Disallow scheduled GitHub Actions run on forked repos#48143
Conversation
|
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format? or See also: |
|
|
|
Thanks @kevinjqliu ! |
|
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit f096d48. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 1 possible false positive for unstable benchmarks that are known to sometimes produce them. |
…repos (apache#48143) ### Rationale for this change Closes apache#48142 Prevents Github workflows to periodically run on forked repos ### What changes are included in this PR? Add a gate to the two github workflows to prevent them from periodically running on forked repos. ### Are these changes tested? Yes, manually ### Are there any user-facing changes? No **This PR includes breaking changes to public APIs.** (If there are any breaking changes to public APIs, please explain which changes are breaking. If not, you can remove this.) **This PR contains a "Critical Fix".** (If the changes fix either (a) a security vulnerability, (b) a bug that caused incorrect or invalid data to be produced, or (c) a bug that causes a crash (even when the API contract is upheld), please provide explanation. If not, you can remove this.) * GitHub Issue: apache#48142 Authored-by: Kevin Liu <kevin.jq.liu@gmail.com> Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
Rationale for this change
Closes #48142
Prevents Github workflows to periodically run on forked repos
What changes are included in this PR?
Add a gate to the two github workflows to prevent them from periodically running on forked repos.
Are these changes tested?
Yes, manually
Are there any user-facing changes?
No
This PR includes breaking changes to public APIs. (If there are any breaking changes to public APIs, please explain which changes are breaking. If not, you can remove this.)
This PR contains a "Critical Fix". (If the changes fix either (a) a security vulnerability, (b) a bug that caused incorrect or invalid data to be produced, or (c) a bug that causes a crash (even when the API contract is upheld), please provide explanation. If not, you can remove this.)