Skip to content

fix merge conflicts for security analytics#3715

Merged
cwillum merged 2 commits into2.6from
backport/backport-3184-to-2.6
Apr 7, 2023
Merged

fix merge conflicts for security analytics#3715
cwillum merged 2 commits into2.6from
backport/backport-3184-to-2.6

Conversation

@cwillum
Copy link
Contributor

@cwillum cwillum commented Apr 7, 2023

Description

Fixes to merge conflicts

Issues Resolved

fixes merge conflicts in #3184

Checklist

  • By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
    For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: cwillum <cwmmoore@amazon.com>
@cwillum cwillum requested a review from a team as a code owner April 7, 2023 21:41
@cwillum cwillum self-assigned this Apr 7, 2023
@cwillum cwillum merged commit 2ba4447 into 2.6 Apr 7, 2023
@github-actions github-actions bot deleted the backport/backport-3184-to-2.6 branch April 7, 2023 21:51
@cwillum cwillum added backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5 labels Apr 7, 2023
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.4 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.4 2.4
# Navigate to the new working tree
pushd ../.worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-3715-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2ba4447b4961d6171f4e131a8eba5c953585b456
# Push it to GitHub
git push --set-upstream origin backport/backport-3715-to-2.4
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.4

Then, create a pull request where the base branch is 2.4 and the compare/head branch is backport/backport-3715-to-2.4.

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.5 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.5 2.5
# Navigate to the new working tree
pushd ../.worktrees/backport-2.5
# Create a new branch
git switch --create backport/backport-3715-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 2ba4447b4961d6171f4e131a8eba5c953585b456
# Push it to GitHub
git push --set-upstream origin backport/backport-3715-to-2.5
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.5

Then, create a pull request where the base branch is 2.5 and the compare/head branch is backport/backport-3715-to-2.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant