From 59ba4b033507061918894097adaf33a466a93e7e Mon Sep 17 00:00:00 2001
From: Alejandro R Mosteo <alejandro@mosteo.com>
Date: Mon, 9 Nov 2020 13:43:28 +0100
Subject: [PATCH] Fix spurious detection of alire.toml during build test (#201)

The detection is correct in the sense that the file is at ./alire/alire.toml,
but it is not an old manifest but the proper manifest of the alire repo. This
is an unexpected and unwanted interaction that should go away once the check
for old manifests is removed. For now, it's simpler to just do the tests in a
clean folder.
---
 scripts/gh-build-crate.sh | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/scripts/gh-build-crate.sh b/scripts/gh-build-crate.sh
index fa94f82d..b5ab9479 100755
--- a/scripts/gh-build-crate.sh
+++ b/scripts/gh-build-crate.sh
@@ -18,6 +18,10 @@ echo Changed files: $CHANGES
 # Import the out-of-docker built alr
 export PATH+=:${PWD}/alire/bin
 
+# Change to a new testing folder to avoid spurious detection of ./alire/alire.toml
+mkdir testdir
+cd testdir
+
 # Show alr metadata
 alr version