Fix autocommiting from CI (elastic#148066)

The new images have an updated gh binary which now requires setting the `GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the env var so that we didn't need to find a good time to execute the CLI (after the keys are in the env, but before all other user code) or worry about the logging. This also allows other users of our scripts to customize as makes sense without having to dive into a bunch of imperative shell code. Co-authored-by: kibanamachine <[email protected]>
kibanamachine · Dec 23, 2022 · 1b8ddc6 · 1b8ddc6
1 parent ffb1dc3
commit 1b8ddc6
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/.buildkite/scripts/common/env.sh b/.buildkite/scripts/common/env.sh
@@ -108,3 +108,6 @@ export BROWSERSLIST_IGNORE_OLD_DATA=true
 export TEST_GROUP_TYPE_UNIT="Jest Unit Tests"
 export TEST_GROUP_TYPE_INTEGRATION="Jest Integration Tests"
 export TEST_GROUP_TYPE_FUNCTIONAL="Functional Tests"
+
+# tells the gh command what our default repo is
+export GH_REPO=github.com/elastic/kibana