From 407942da3febaa44960c8ad5509748fa3c4311ff Mon Sep 17 00:00:00 2001 From: Richard Brooksby Date: Sat, 14 Jan 2023 12:58:49 +0000 Subject: [PATCH] Explaining where to look for build results in step 6. --- mps/procedure/pull-request-merge.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/mps/procedure/pull-request-merge.rst b/mps/procedure/pull-request-merge.rst index feb2c92a23b..251d27d23ec 100644 --- a/mps/procedure/pull-request-merge.rst +++ b/mps/procedure/pull-request-merge.rst @@ -267,13 +267,14 @@ These steps will only rarely need repeating. - there were failed or missing build results from CI then push the merge to a fresh branch in the `Ravenbrook MPS repo - on GitHub`_ to trigger CI to build and testing on all target - platforms. :: + on GitHub`_. This should trigger CI to build and testing on all + target platforms. :: git push github merge/2023-01-06/speed-hax - You will need to wait for results from CI. [Add details of how to - see them. RB 2023-07-01] + You will need to wait for results from CI. Look for a build + results in the `Travis CI build history for the repo`_ and in the + `GitHub workflows for the repo`_. See build (step 5) about what to do if tests do not pass.