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

docs: Update release notes for 2.9.8 #12881

Merged
merged 1 commit into from
May 3, 2024
Merged

docs: Update release notes for 2.9.8 #12881

merged 1 commit into from
May 3, 2024

Conversation

JStickler
Copy link
Contributor

What this PR does / why we need it:

Updates the Release Notes for version 2.9.8.

@JStickler JStickler added type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories backport release-2.9.x backport release-3.0.x labels May 3, 2024
@JStickler JStickler requested a review from a team as a code owner May 3, 2024 17:02
@grafanabot
Copy link
Collaborator

This PR must be merged before a backport PR will be created.

2 similar comments
@grafanabot
Copy link
Collaborator

This PR must be merged before a backport PR will be created.

@grafanabot
Copy link
Collaborator

This PR must be merged before a backport PR will be created.

@JStickler JStickler merged commit a21c107 into main May 3, 2024
64 checks passed
@JStickler JStickler deleted the RN_298 branch May 3, 2024 19:47
grafanabot pushed a commit that referenced this pull request May 3, 2024
@grafanabot
Copy link
Collaborator

The backport to release-3.0.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-12881-to-release-3.0.x origin/release-3.0.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x a21c1077deecfb6b7a68a2ba6e472cafc2a2eca3

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-12881-to-release-3.0.x
# Create the PR body template
PR_BODY=$(gh pr view 12881 --json body --template 'Backport a21c1077deecfb6b7a68a2ba6e472cafc2a2eca3 from #12881{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "chore: [release-3.0.x] docs: Update release notes for 2.9.8" --body-file - --label "size/XS" --label "type/docs" --label "backport" --base release-3.0.x --milestone release-3.0.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-12881-to-release-3.0.x

# Create a pull request where the `base` branch is `release-3.0.x` and the `compare`/`head` branch is `backport-12881-to-release-3.0.x`.

# Remove the local backport branch
git switch main
git branch -D backport-12881-to-release-3.0.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release-2.9.x backport release-3.0.x backport-failed size/XS type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants