lane with the same id already exists #28

When I create a pull request, this action assigns a lane in bit cloud as it should, but often when I make a push to the same branch with corrections, it gives this output:
a lane with the same id (flinten.test/pr-1) already exists with a different hash unexpected network error has occurred.

I would like it to add the corrections in bit cloud lane to.

Is this a bug or have I misunderstood the use of this action?