In Gearset Pipelines, if a PR validation is already in progress and a new commit is pushed to the same feature branch, Gearset does not automatically trigger a follow-up validation for the latest commit after the current run completes. This leaves GitHub showing “checks not triggered yet” for the newest commit until we manually re-run validation.

Expected behavior:

When a new commit is pushed while validation is running, Gearset should automatically schedule/trigger another validation after the current run finishes (or cancel + restart, depending on design), so the latest commit is always validated without manual intervention.

Actual behavior:

The in-progress validation completes for the earlier commit, and the newer commit pushed during the run does not trigger validation automatically. We must manually re-run validation.

Steps to reproduce:

Open a PR from a feature branch with a validation step configured in Gearset Pipelines (commit-triggered).
Push commit A; validation starts.
While validation is still running, push commit B to the same branch.
Observe that the running validation completes for commit A and no automatic validation starts for commit B.

Notes / Observations:

If the validation is queued (not yet started), it appears to use the latest commit when it eventually runs.

The issue happens consistently when the validation is actively running.

Impact:

PR can appear “green” for an older commit while newer unvalidated changes exist.
Adds manual effort and increases risk of merging unvalidated changes.

Workaround:

Manually re-run validation after pushing commits during an active validation.