tree 1a0944fc11cdebe296d859031508551960e9be37
parent 6871646a50f0045fa1885023124e0a429c9e63c8
author Lari Hotari <lhotari@users.noreply.github.com> 1612836785 +0200
committer GitHub <noreply@github.com> 1612836785 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgIe+xCRBK7hj4Ov3rIwAAdHIIAIrHjzT5HSWW/E08r/3ajQxk
 pPMoMlwE8QfhvFrt8cNOQPvZrJfJsCqTVqzeVpquhg5hBL8b+HmH2qgLq3Dd9M2t
 h6v8tfnwIekJnFuIFd6SrWdDcgJELmHIKUYntzsERCBQXHUhzyLjVmazMcvt5GpM
 g4YC5ogwe5L4eRYO96jVh5KmfjMSbClTssx/fIzZWMCIxPUc9bd6h4ASF2zF56jq
 Zzo6+2l3vrBCk+pc3/cWgSHYh04Dx/a7uB08Cx6bEi5LGZoY6eCTdTztpjL+KkUo
 9oHejLeTsv5laUfziMm44rdCdOS2YylVPxOcCiGv/AehFXadzZq3TFqi9kbB5cA=
 =2Hs2
 -----END PGP SIGNATURE-----
 

Set 'changed_only' to 'no' if commits cannot be found in diff-only action (#16)

Fixes #12 https://github.com/apache/pulsar/issues/9526

The current solution causes the build to skip tests in Pulsar builds when the pull request commits cannot be found. It's better that diff-only script sets 'changed_only' to 'no' when it's not able to determine the correct result.

The commit for a PR won't be found when shallow clones are used and there are more commits in the PR than the depth of the shallow clone. The Pulsar GitHub Action workflows use shallow clone with the depth of 25 commits. This PR will support such PRs by defaulting to `changed_only` to `no` when the commit cannot be found.

This PR also fixes support for non-PR events such as `push` event. `changed_only` is set to `no` when the triggering event isn't a `pull_request` event.