Fix autocommiting from CI (#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 <42973632+kibanamachine@users.noreply.github.com>
This commit is contained in:
Spencer 2022-12-23 09:31:54 -07:00 committed by GitHub
parent ffb1dc3e28
commit 1b8ddc6267
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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