[DOC] Updated examples for filtered tag values#4425
Merged
knylander-grafana merged 2 commits intografana:mainfrom Dec 10, 2024
knylander-grafana:4423-remove-unscoped-example-api-search-v2
Merged
[DOC] Updated examples for filtered tag values#4425knylander-grafana merged 2 commits intografana:mainfrom knylander-grafana:4423-remove-unscoped-example-api-search-v2
knylander-grafana merged 2 commits intografana:mainfrom
knylander-grafana:4423-remove-unscoped-example-api-search-v2
Conversation
Contributor
|
This PR must be merged before a backport PR will be created. |
1 similar comment
Contributor
|
This PR must be merged before a backport PR will be created. |
mentaman
reviewed
Dec 6, 2024
mdisibio
approved these changes
Dec 10, 2024
Contributor
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-4425-to-release-v2.6 origin/release-v2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x fe8bb268d1d211856bc10639ee4617a6a3f05d43When the conflicts are resolved, stage and commit the changes: If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-4425-to-release-v2.6
# Create the PR body template
PR_BODY=$(gh pr view 4425 --json body --template 'Backport fe8bb268d1d211856bc10639ee4617a6a3f05d43 from #4425{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release-v2.6] [DOC] Updated examples for filtered tag values' --body-file - --label 'type/docs' --label 'backport' --base release-v2.6 --milestone release-v2.6 --webOr, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-4425-to-release-v2.6
# Create a pull request where the `base` branch is `release-v2.6` and the `compare`/`head` branch is `backport-4425-to-release-v2.6`.
# Remove the local backport branch
git switch main
git branch -D backport-4425-to-release-v2.6 |
3 tasks
Contributor
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-4425-to-release-v2.7 origin/release-v2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x fe8bb268d1d211856bc10639ee4617a6a3f05d43When the conflicts are resolved, stage and commit the changes: If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-4425-to-release-v2.7
# Create the PR body template
PR_BODY=$(gh pr view 4425 --json body --template 'Backport fe8bb268d1d211856bc10639ee4617a6a3f05d43 from #4425{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release-v2.7] [DOC] Updated examples for filtered tag values' --body-file - --label 'type/docs' --label 'backport' --base release-v2.7 --milestone release-v2.7 --webOr, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-4425-to-release-v2.7
# Create a pull request where the `base` branch is `release-v2.7` and the `compare`/`head` branch is `backport-4425-to-release-v2.7`.
# Remove the local backport branch
git switch main
git branch -D backport-4425-to-release-v2.7 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does:
Updates the filtered tag values example under Search tag values V2 section of the Tempo HTTP API documentation.
Which issue(s) this PR fixes:
Part of #4423
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]