Open shnizzedy opened 11 months ago
These triggers https://github.com/FCP-INDI/C-PAC/blob/de6407454d35e0cbf0434f7bc34fe44b924e2819/.github/workflows/regression_test_lite.yml#L3-L17 lead to duplicate run attempts and this conditional https://github.com/FCP-INDI/C-PAC/blob/de6407454d35e0cbf0434f7bc34fe44b924e2819/.github/workflows/regression_test_lite.yml#L40 intended to prevent this behavior is not preventing it.
0 or 1 ACCESS runs is attempted on PRs
- opened - ready_for_review - reopened
coming from branches or forks and targeting develop
develop
As an alternative to these triggers, we could trigger after the changes are merged into develop
Describe the bug
These triggers https://github.com/FCP-INDI/C-PAC/blob/de6407454d35e0cbf0434f7bc34fe44b924e2819/.github/workflows/regression_test_lite.yml#L3-L17 lead to duplicate run attempts and this conditional https://github.com/FCP-INDI/C-PAC/blob/de6407454d35e0cbf0434f7bc34fe44b924e2819/.github/workflows/regression_test_lite.yml#L40 intended to prevent this behavior is not preventing it.
To reproduce
Expected behavior
0 or 1 ACCESS runs is attempted on PRs
coming from branches or forks and targeting
develop
Acceptance criteria
Screenshots
Additional context
As an alternative to these triggers, we could trigger after the changes are merged into
develop