-
Notifications
You must be signed in to change notification settings - Fork 508
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
Rework Clients, Tools, and Data Prepper section #1794
Conversation
Signed-off-by: Naarcha-AWS <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@kolchfa-aws - Did you want to change the order of the list of clients? Python, .NET, Ruby, etc.? Or should we alphabetize them? |
We would like to revisit this order and just list languages. I will reorganize these pages after the 2.4 release. |
OK, then we just need to move Grafana to Tools. Thanks! |
Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
The backport to
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-1794-to-2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4d6a2759508d3b7e318e353281676cabb9bb8f9e
# Push it to GitHub
git push --set-upstream origin backport/backport-1794-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 |
The backport to
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-1794-to-2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4d6a2759508d3b7e318e353281676cabb9bb8f9e
# Push it to GitHub
git push --set-upstream origin backport/backport-1794-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 |
The backport to
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-1794-to-2.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 4d6a2759508d3b7e318e353281676cabb9bb8f9e
# Push it to GitHub
git push --set-upstream origin backport/backport-1794-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 |
* Rework Clients, Tools, and Data Prepper section Signed-off-by: Naarcha-AWS <[email protected]> * Add new Data Prepper files Signed-off-by: Naarcha-AWS <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> (cherry picked from commit 4d6a275)
* Rework Clients, Tools, and Data Prepper section Signed-off-by: Naarcha-AWS <[email protected]> * Add new Data Prepper files Signed-off-by: Naarcha-AWS <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> (cherry picked from commit 4d6a275) Co-authored-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS [email protected]
Closes part of #1036
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.