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

Rename Creating Benchmark workloads page #6807

Merged
merged 2 commits into from
Mar 29, 2024
Merged

Conversation

Naarcha-AWS
Copy link
Collaborator

Renames the creating workloads page based on customer feedback.

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.

@Naarcha-AWS
Copy link
Collaborator Author

@IanHoang: This is ready for your review.

@Naarcha-AWS Naarcha-AWS added the 3 - Tech review PR: Tech review in progress label Mar 28, 2024
@peterzhuamazon peterzhuamazon merged commit 65a5e9d into main Mar 29, 2024
4 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Mar 29, 2024
Signed-off-by: Archer <[email protected]>
(cherry picked from commit 65a5e9d)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@peterzhuamazon peterzhuamazon deleted the rename-custom-workloads branch March 29, 2024 22:03
peterzhuamazon pushed a commit that referenced this pull request Mar 29, 2024
(cherry picked from commit 65a5e9d)

Signed-off-by: Archer <[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
Labels
3 - Tech review PR: Tech review in progress backport 2.12 PR: Backport label for 2.12 benchmark
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants