docs/handbook/testing/setup.md

@@ -144,25 +144,36 @@ Ensure submodules are up to date.
 make update
 ```
 
-Commit test files to the main branch of the test data repository.
+Commit new or modified test files to a new branch of the test data repository.
 ``` bash
 cd tests/data
 git checkout main
-.. make any changes ..
+git checkout -B add-x-tests
+.. make your changes ..
 git commit testfile1 testfile2
+git push origin add-x-tests
 ```
 
-Commit changes in the Blender repository, including the updated `tests/data` submodule hash.
+Commit changes to your fork of the Blender repository, including the updated
+`tests/data` submodule hash, and create a pull request.
 ``` bash
 cd ../..
+git checkout -B add-x-tests
 git commit sourcefile1 sourcefile2 tests/data
+git push me
+.. then create a pull request from this branch ..
 ```
 
-Check everything is ok, and push to both repositories.
+Ensure your tests pass on the build bot commenting `@blender-bot build`,
+or `@blender-bot build +gpu` to also run GPU tests (these aren't tested
+regularly, so some GPU tests you havn't modified may fail), in your pull request.
+
+If the tests pass, then push your changes in the test data repo to the
+main branch, update your branch of the Blender repo to point to the updated tests,
+then push your Blender chages to the main branch of the Blender repo.
+
 ``` bash
-cd tests/data
-git push origin main
-cd ../..
-git push origin main
+TODO: Add commands?
+I personally haven't done merging/squishing of branches into main so I'm not sure the correct approach here. 
 ```