Is your feature request related to a problem? Please describe.
When I send a commit, a new build preview is created at Amplify console, starting the Github check. If I send another commit while the old builds are running, the check is queued and will remain so until we send another commit. That's because a new build is created and the old one is not cancelled.
Describe the solution you'd like
I think we should cancel the current build if a new one is created.This will solve or problem with github amplify check.
Additional context
When I send a new push with the build still running.

@netochaves For clarification how are you triggering this behavior?
(1) Create a pull request (build triggered)--> Commit some changes (before pull request build finishes)
OR
(2) Create a pull request (build triggered) --> Create another pull request (subsequent build triggered)
OR
(3) Commit some changes (build triggered) --> commit some more changes
@netochaves I tried:
(1) creating a PR with PR preview enabled --> then I made a commit to my master branch and I wasn't able to reproduce this issue.
Option one, but you've to commit on PR.
@ganipcanot Create a pull request (build triggered) => Commit some changes on the same PR (before pull request build finishes)
@netochaves So you created a pull request (build triggered) => commit some changes to the PR branch => at this point you do a git push (to update the remote repository/branch)?
I was able to reproduce this and I am adding it to our backlog for further investigation - thanks for letting us know!
We are also seeing this issue with about 20% of our Pull Requests.
This is a problem for us as well. Do you have an ETA on a fix?
I'm also experiencing this issue.
I'm able to reproduce this consistently via the following two scenarios (let's assume master branch triggers the preview to be built):
In both of the above cases, preview builds become stuck without resolution.
Most helpful comment
We are also seeing this issue with about 20% of our Pull Requests.