-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
ci: fix logql analyzer #14511
ci: fix logql analyzer #14511
Conversation
Signed-off-by: Vladyslav Diachenko <[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
Signed-off-by: Vladyslav Diachenko <[email protected]>
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-14511-to-release-3.2.x origin/release-3.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 311797442f0a402b388904ee346f4ee411e8ab03 When 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-14511-to-release-3.2.x
# Create the PR body template
PR_BODY=$(gh pr view 14511 --json body --template 'Backport 311797442f0a402b388904ee346f4ee411e8ab03 from #14511{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'ci: fix logql analyzer (backport release-3.2.x)' --body-file - --label 'size/S' --label 'type/bug' --label 'backport' --base release-3.2.x --milestone release-3.2.x --web Or, 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-14511-to-release-3.2.x
# Create a pull request where the `base` branch is `release-3.2.x` and the `compare`/`head` branch is `backport-14511-to-release-3.2.x`.
# Remove the local backport branch
git switch main
git branch -D backport-14511-to-release-3.2.x |
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-14511-to-release-3.1.x origin/release-3.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 311797442f0a402b388904ee346f4ee411e8ab03 When 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-14511-to-release-3.1.x
# Create the PR body template
PR_BODY=$(gh pr view 14511 --json body --template 'Backport 311797442f0a402b388904ee346f4ee411e8ab03 from #14511{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'ci: fix logql analyzer (backport release-3.1.x)' --body-file - --label 'size/S' --label 'type/bug' --label 'backport' --base release-3.1.x --milestone release-3.1.x --web Or, 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-14511-to-release-3.1.x
# Create a pull request where the `base` branch is `release-3.1.x` and the `compare`/`head` branch is `backport-14511-to-release-3.1.x`.
# Remove the local backport branch
git switch main
git branch -D backport-14511-to-release-3.1.x |
Signed-off-by: Vladyslav Diachenko <[email protected]> Co-authored-by: Vladyslav Diachenko <[email protected]> (cherry picked from commit 3117974)
Signed-off-by: Vladyslav Diachenko <[email protected]> Co-authored-by: Vladyslav Diachenko <[email protected]> (cherry picked from commit 3117974)
What this PR does / why we need it:
Fix the LogQL Analyzer CI
Special notes for your reviewer:
Checklist
CONTRIBUTING.md
guide (required)feat
PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.md
deprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR