Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Github Action for backport #122479

Merged
merged 1 commit into from
Jan 7, 2022
Merged

Update Github Action for backport #122479

merged 1 commit into from
Jan 7, 2022

Conversation

sorenlouv
Copy link
Member

Related #122119

@sorenlouv sorenlouv requested a review from a team as a code owner January 6, 2022 23:23
@sorenlouv sorenlouv added backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes v8.1.0 labels Jan 6, 2022
@sorenlouv sorenlouv enabled auto-merge (squash) January 6, 2022 23:24
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@sorenlouv sorenlouv merged commit 5316d08 into elastic:main Jan 7, 2022
@sorenlouv sorenlouv deleted the update-backport-action branch January 7, 2022 06:34
@sorenlouv sorenlouv added auto-backport Deprecated - use backport:version if exact versions are needed and removed backport:skip This commit does not require backporting labels Jan 7, 2022
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Jan 7, 2022
@kibanamachine
Copy link
Contributor

💔 Backport failed

The pull request could not be backported due to the following error:
There are no branches to backport to. Aborting.

How to fix

Re-run the backport manually:

node scripts/backport --pr 122479

Questions ?

Please refer to the Backport tool documentation

@sorenlouv sorenlouv added v8.0.0 v7.16.0 auto-backport Deprecated - use backport:version if exact versions are needed and removed backport:skip This commit does not require backporting auto-backport Deprecated - use backport:version if exact versions are needed labels Jan 7, 2022
@kibanamachine
Copy link
Contributor

💔 Some backports could not be created

Status Branch Result
❌ 8.0 Backport failed because of merge conflicts
❌ 7.16 Backport failed because of merge conflicts

You might need to backport the following PRs to 7.16:
- chore(NA): adds 7.16 into backportrc

How to fix

Re-run the backport manually:

node scripts/backport --pr 122479

Questions ?

Please refer to the Backport tool documentation

@sorenlouv
Copy link
Member Author

💔 Some backports could not be created

Status Branch Result
❌ 7.16 variables is not defined

How to fix

Re-run the backport manually:

node scripts/backport --pr 122479

Questions ?

Please refer to the Backport tool documentation

@kibanamachine kibanamachine mentioned this pull request Jan 7, 2022
Merged
1 task
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jan 10, 2022
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 122479 or prevent reminders by adding the backport:skip label.

@sorenlouv sorenlouv added auto-backport Deprecated - use backport:version if exact versions are needed v7.16.0 and removed v7.16.0 v8.0.0 auto-backport Deprecated - use backport:version if exact versions are needed labels Jan 10, 2022
@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
❌ 7.16 Backport failed because of merge conflicts

How to fix

Re-run the backport manually:

node scripts/backport --pr 122479

Questions ?

Please refer to the Backport tool documentation

@sorenlouv sorenlouv added backport:skip This commit does not require backporting and removed backport missing Added to PRs automatically when the are determined to be missing a backport. auto-backport Deprecated - use backport:version if exact versions are needed v7.16.0 labels Jan 10, 2022
gbamparop pushed a commit to gbamparop/kibana that referenced this pull request Jan 12, 2022
@sorenlouv @gbamparop
Update Github Action for backport (elastic#122479)
6fae006
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@brianseeders brianseeders brianseeders approved these changes

Assignees
No one assigned
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes v8.1.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@sorenlouv @kibana-ci @kibanamachine @brianseeders