All committers have signed the CLA.

I would like it if I did not have to continuously answer this question for people. They don't see the warning about it in the github actions readme.

So... you are on board with the idea? 😅 not entirely sure if i got the intention right

@bahmutov thoughts?

I am not sure I understand what this PR changes. There is refactoring, but ultimately we still use the same ciBuildId, no? How would it change anything the user has to do?

@bahmutov this ciBuildId was only used when either group or parallel options were used. This PR refactors this and starts using it for all scenarios (minus when the explicit ciBuildId is given, of course)

@Andarist do you have a situation that without this PR it does NOT create a new test run? I am trying this right now in https://github.com/bahmutov/cypress-gh-action-small-example and it creates new dashboard runs on every re-run just fine, no?

I'm using this in a private repo - I could try to set up a public repro later if you will require that.

I've tracked down my workflow runs from before I've fixed this on our side and I got:

The run you are attempting to access is already complete and will not accept new groups.

The existing run is: xxxx

When a run finishes all of its groups, it waits for a configurable set of time before finally completing. You must add more groups during that time period.

The --tag flag you passed was: 
The --group flag you passed was: integration

Which was a result of re-running the workflow manually from the GitHub interface. I've resolved this on our side by generating a ciBuildId with a date in it:

- command: yarn ci:test:integration:cypress
+ command: yarn ci:test:integration:cypress -- --ci-build-id ${{ steps.date.outputs.date }}

which has fixed the issue.