Fix autocommiting from CI #148066
Merged
Fix autocommiting from CI #148066
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
⏳ Build in-progress, with failuresFailed CI StepsHistoryTo update your PR or re-run it, just comment with: |
added 2 commits
December 23, 2022 09:17
spalger
force-pushed
the
test-auto-commit
branch
from
e68aa07 to
3701ff3
Compare
spalger
changed the title
spalger
added
the
release_note:skip
spalger
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 23, 2022
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]> (cherry picked from commit 1b8ddc6)
This was referenced Dec 23, 2022
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 23, 2022
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]> (cherry picked from commit 1b8ddc6)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Dec 23, 2022
# Backport This will backport the following commits from `main` to `8.5`: - [Fix autocommiting from CI (#148066)](#148066) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Spencer","email":"[email protected]"},"sourceCommit":{"committedDate":"2022-12-23T16:31:54Z","message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v8.7.0"],"number":148066,"url":"https://github.com/elastic/kibana/pull/148066","mergeCommit":{"message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148066","number":148066,"mergeCommit":{"message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419"}}]}] BACKPORT--> Co-authored-by: Spencer <[email protected]>
kibanamachine
added a commit
that referenced
this pull request
Dec 23, 2022
# Backport This will backport the following commits from `main` to `8.6`: - [Fix autocommiting from CI (#148066)](#148066) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Spencer","email":"[email protected]"},"sourceCommit":{"committedDate":"2022-12-23T16:31:54Z","message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v8.7.0"],"number":148066,"url":"https://github.com/elastic/kibana/pull/148066","mergeCommit":{"message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148066","number":148066,"mergeCommit":{"message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419"}}]}] BACKPORT--> Co-authored-by: Spencer <[email protected]>
spalger
pushed a commit
that referenced
this pull request
Dec 23, 2022
# Backport This will backport the following commits from `main` to `7.17`: - [Fix autocommiting from CI (#148066)](#148066) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Spencer","email":"[email protected]"},"sourceCommit":{"committedDate":"2022-12-23T16:31:54Z","message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v8.7.0"],"number":148066,"url":"https://github.com/elastic/kibana/pull/148066","mergeCommit":{"message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148066","number":148066,"mergeCommit":{"message":"Fix autocommiting from CI (#148066)\n\nThe new images have an updated gh binary which now requires setting the\r\n`GITHUB_REPO` env var, or calling `gh repo set-default`. I opted for the\r\nenv var so that we didn't need to find a good time to execute the CLI\r\n(after the keys are in the env, but before all other user code) or worry\r\nabout the logging. This also allows other users of our scripts to\r\ncustomize as makes sense without having to dive into a bunch of\r\nimperative shell code.\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"1b8ddc626765af542d4270bdb372a6e8bec14419"}},{"url":"https://github.com/elastic/kibana/pull/148068","number":148068,"branch":"8.5","state":"OPEN"},{"url":"https://github.com/elastic/kibana/pull/148069","number":148069,"branch":"8.6","state":"OPEN"}]}] BACKPORT-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new images have an updated gh binary which now requires setting the
GITHUB_REPOenv var, or callinggh 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.