From 9b16ce355debd105b65bb841b300e585e80aefad Mon Sep 17 00:00:00 2001
From: Yann Dirson <yann.dirson@vates.fr>
Date: Mon, 29 Jan 2024 16:00:29 +0100
Subject: [PATCH] ci/everycommit: add a "git status" call to investigate build
 failures

Errors reported by git-rebase actually happen after a first build was run,
which seems to point to the build modifying source files.

Signed-off-by: Yann Dirson <yann.dirson@vates.fr>
---
 .gitlab-ci.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 31dcf11..0d4d164 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -184,6 +184,7 @@ build-linux-everycommit:
     # failing commit)
     - git rebase --rebase-merges $CI_MERGE_REQUEST_DIFF_BASE_SHA
       --exec 'devscripts/gitlab-ci-runbuild.sh cargo build ${FEATURES} ${CARGO_FLAGS}'
+      --exec 'git status'
   after_script:
     # since Git Strategy is "fetch", avoid poluting subsequent runs
     # (but as of v16.9 it still won't be run on timeout or cancel)
-- 
2.39.5