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.

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

Remove logos for page examples #639

Merged
merged 1 commit into from
Mar 29, 2023

Conversation

AbhishekReddy1127
Copy link
Contributor

Description

Removed logos for the all examples in the section page.

Screenshot 2023-03-28 at 1 29 56 PM

Issues Resolved

Fixes #625

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • All tests pass
    • yarn lint
    • yarn test-unit
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: AbhishekReddy1127 <[email protected]>
@AbhishekReddy1127 AbhishekReddy1127 marked this pull request as ready for review March 29, 2023 16:08
@AbhishekReddy1127 AbhishekReddy1127 requested a review from a team as a code owner March 29, 2023 16:08
Copy link
Contributor

@KrooshalUX KrooshalUX left a comment

Choose a reason for hiding this comment

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

LGTM

@joshuarrrr
Copy link
Member

@AbhishekReddy1127 Do we backport doc site changes, or just skip?

@opensearch-trigger-bot
Copy link

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

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

@opensearch-trigger-bot
Copy link

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

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-639-to-1.x.

@opensearch-trigger-bot
Copy link

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

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

@opensearch-trigger-bot
Copy link

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

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

@opensearch-trigger-bot
Copy link

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

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-639-to-1.x.

@BSFishy
Copy link
Contributor

BSFishy commented May 9, 2023

Can be backported when #753 gets pushed through

@opensearch-trigger-bot
Copy link

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

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

opensearch-trigger-bot bot pushed a commit that referenced this pull request May 10, 2023
Signed-off-by: AbhishekReddy1127 <[email protected]>
(cherry picked from commit ead8cb0)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
BSFishy pushed a commit that referenced this pull request May 10, 2023
(cherry picked from commit ead8cb0)

Signed-off-by: AbhishekReddy1127 <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
opensearch-trigger-bot bot pushed a commit that referenced this pull request Jun 26, 2023
Signed-off-by: AbhishekReddy1127 <[email protected]>
(cherry picked from commit ead8cb0)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
joshuarrrr pushed a commit that referenced this pull request Jun 28, 2023
(cherry picked from commit ead8cb0)

Signed-off-by: AbhishekReddy1127 <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(OUI Docs) Remove logos from Page title on /layout/page
5 participants