If a developer needs to add or modify an end to end test in the blazingsql repo, then they need to make changes to the testing files in the blazingsql-testing-files repo via a PR. That PR branch must be on their fork and must have the same branch name as the branch from their PR.
We need to update test.sh which makes a checkout/clone of blazingsql-testing-files. Before doing that checkout/clone the script should see if a branch exists on the PR author's fork that has the same name as the PR's branch. If that branch exists, then the checkout/clone should be for that branch, otherwise it should be for the blazingsql-testing-files branch that matches the target of the PR in blazingsql, meaning branch-0.X.
We also need to therefore make sure blazingsql-testing-files also has a branch for matching version for different blazing branches e.g. for branch-0.19, branch-0.20 and we need to keep it up to date with whatever the latest branch is
If a developer needs to add or modify an end to end test in the blazingsql repo, then they need to make changes to the testing files in the blazingsql-testing-files repo via a PR. That PR branch must be on their fork and must have the same branch name as the branch from their PR.
We need to update test.sh which makes a checkout/clone of blazingsql-testing-files. Before doing that checkout/clone the script should see if a branch exists on the PR author's fork that has the same name as the PR's branch. If that branch exists, then the checkout/clone should be for that branch, otherwise it should be for the blazingsql-testing-files branch that matches the target of the PR in blazingsql, meaning branch-0.X.
We also need to therefore make sure blazingsql-testing-files also has a branch for matching version for different blazing branches e.g. for branch-0.19, branch-0.20 and we need to keep it up to date with whatever the latest branch is