Skip to content

[DOC] Update Exploring data subpages#2671

Merged
vagimeli merged 1 commit intomainfrom
2670-update-subpages
Feb 6, 2023
Merged

[DOC] Update Exploring data subpages#2671
vagimeli merged 1 commit intomainfrom
2670-update-subpages

Conversation

@vagimeli
Copy link
Contributor

@vagimeli vagimeli commented Feb 6, 2023

Signed-off-by: vagimeli vagimeli@amazon.com

Description

Update TOC subpages

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

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: vagimeli <vagimeli@amazon.com>
@vagimeli vagimeli requested a review from a team as a code owner February 6, 2023 21:38
@vagimeli vagimeli self-assigned this Feb 6, 2023
@vagimeli vagimeli added backport 1.3 PR: Backport label for v1.3.x backport 2.0 PR: Backport label for v2.0.x backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2 backport 2.3 PR: Backport label for 2.3 backport 2.4 PR: Backport label for 2.4 backport 2.5 PR: Backport label for 2.5 labels Feb 6, 2023
Copy link
Contributor

@alicejw1 alicejw1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vagimeli vagimeli merged commit 79e489e into main Feb 6, 2023
@opensearch-trigger-bot
Copy link
Contributor

The backport to 1.3 failed:

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

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-1.3 1.3
# Navigate to the new working tree
cd .worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-2671-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79e489e5039ebff602b45b7d999cbdb05758b25a
# Push it to GitHub
git push --set-upstream origin backport/backport-2671-to-1.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.0 failed:

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

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.0 2.0
# Navigate to the new working tree
cd .worktrees/backport-2.0
# Create a new branch
git switch --create backport/backport-2671-to-2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79e489e5039ebff602b45b7d999cbdb05758b25a
# Push it to GitHub
git push --set-upstream origin backport/backport-2671-to-2.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.0

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.1 failed:

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

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.1 2.1
# Navigate to the new working tree
cd .worktrees/backport-2.1
# Create a new branch
git switch --create backport/backport-2671-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79e489e5039ebff602b45b7d999cbdb05758b25a
# Push it to GitHub
git push --set-upstream origin backport/backport-2671-to-2.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.1

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.2 failed:

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

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.2 2.2
# Navigate to the new working tree
cd .worktrees/backport-2.2
# Create a new branch
git switch --create backport/backport-2671-to-2.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79e489e5039ebff602b45b7d999cbdb05758b25a
# Push it to GitHub
git push --set-upstream origin backport/backport-2671-to-2.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.2

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

@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.3 failed:

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

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.3 2.3
# Navigate to the new working tree
cd .worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-2671-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 79e489e5039ebff602b45b7d999cbdb05758b25a
# Push it to GitHub
git push --set-upstream origin backport/backport-2671-to-2.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.3

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

opensearch-trigger-bot bot pushed a commit that referenced this pull request Feb 6, 2023
Signed-off-by: vagimeli <vagimeli@amazon.com>
(cherry picked from commit 79e489e)
opensearch-trigger-bot bot pushed a commit that referenced this pull request Feb 6, 2023
Signed-off-by: vagimeli <vagimeli@amazon.com>
(cherry picked from commit 79e489e)
vagimeli added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: vagimeli <vagimeli@amazon.com>
(cherry picked from commit 79e489e)

Co-authored-by: Melissa Vagi <105296784+vagimeli@users.noreply.github.com>
vagimeli added a commit that referenced this pull request Feb 6, 2023
Signed-off-by: vagimeli <vagimeli@amazon.com>
(cherry picked from commit 79e489e)

Co-authored-by: Melissa Vagi <105296784+vagimeli@users.noreply.github.com>
@vagimeli vagimeli deleted the 2670-update-subpages branch February 7, 2023 00:02
@vagimeli vagimeli changed the title [DOC] Update TOC subpages [DOC] Update Exploring data subpages Feb 7, 2023
vagimeli added a commit that referenced this pull request Feb 7, 2023
Signed-off-by: vagimeli <vagimeli@amazon.com>
(cherry picked from commit 79e489e)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 1.3 PR: Backport label for v1.3.x backport 2.0 PR: Backport label for v2.0.x backport 2.1 PR: Backport label for 2.1 backport 2.2 PR: Backport label for 2.2 backport 2.3 PR: Backport label for 2.3 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.

3 participants