Greg Bergé

Unfortunately the GitHub Actions API does not give us enough information to build that feature. We can't determine what jobs correspond to a specific shard, it means we can't determine...

Finally found a way to do it!

@alexbjorlig it's now supported. Be sure to set [`PARALLEL_INDEX`](https://argos-ci.com/docs/parallel-testing) (if you use Playwright reporter it's automatic) and to upgrade your SDK to the latest version.

We will not do it, it's not the focus of Argos.

Hello @oliviertassinari, it's very interesting. It could dramatically speed up the build time for you! I will think about it and I keep you up to date.

Chromatic does it yes but they have the control over Storybook so it's integrated. https://www.chromatic.com/docs/turbosnap/ For Argos we can't make it automatic that's why it's not a urgent issue. For...

Hi @cherniavskii, your use case is correct, we will work on multi reference branch support soon. For now you should ignore Argos on master branch or even don't run it....

## Implementation The column `referenceBranch` in the database should no be a RegExp. We use it twice: https://github.com/argos-ci/argos/blob/87086299dbb354feb3cc1dfa712c4d82207f1b1f/apps/build/src/createBuildDiffs.ts#L25 Easy to replace it with a RegExp. And in the `baseCompare` process...

I think we can just use the branch specified in PR if the mode is set to automatic from GitHub to solve this. - If the reference branch is inferred...

Needed by someone.