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

Fix links to the migrating guide. #520

Merged
merged 1 commit into from
Jul 20, 2023
Merged

Fix links to the migrating guide. #520

merged 1 commit into from
Jul 20, 2023

Conversation

mikelittle
Copy link
Contributor

All the upgrading guides had a broken link.

@mikelittle mikelittle merged commit 88edcb0 into master Jul 20, 2023
3 checks passed
@mikelittle mikelittle deleted the fix-migrating-link branch July 20, 2023 11:52
@hm-backport
Copy link

hm-backport bot commented Jul 20, 2023

The backport to v12-branch failed:

Commits ["6d306aee6abd888bc47d54399fc8787ccd158337"] could not be cherry-picked on top of v12-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v12-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick 6d306aee6abd888bc47d54399fc8787ccd158337
# Create a new branch with these backported commits.
git checkout -b backport-520-to-v12-branch
# Push it to GitHub.
git push --set-upstream origin backport-520-to-v12-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v12-branch and the compare/head branch is backport-520-to-v12-branch.

@hm-backport
Copy link

hm-backport bot commented Jul 20, 2023

The backport to v13-branch failed:

Commits ["6d306aee6abd888bc47d54399fc8787ccd158337"] could not be cherry-picked on top of v13-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v13-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick 6d306aee6abd888bc47d54399fc8787ccd158337
# Create a new branch with these backported commits.
git checkout -b backport-520-to-v13-branch
# Push it to GitHub.
git push --set-upstream origin backport-520-to-v13-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v13-branch and the compare/head branch is backport-520-to-v13-branch.

@hm-backport
Copy link

hm-backport bot commented Jul 20, 2023

The backport to v14-branch failed:

Commits ["6d306aee6abd888bc47d54399fc8787ccd158337"] could not be cherry-picked on top of v14-branch

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub.
git fetch
# Create new working tree.
git worktree add .worktrees/backport v14-branch
# Navigate to the new directory.
cd .worktrees/backport
# Cherry-pick all the commits of this pull request and resolve the likely conflicts.
git cherry-pick 6d306aee6abd888bc47d54399fc8787ccd158337
# Create a new branch with these backported commits.
git checkout -b backport-520-to-v14-branch
# Push it to GitHub.
git push --set-upstream origin backport-520-to-v14-branch
# Go back to the original working tree.
cd ../..
# Delete the working tree.
git worktree remove .worktrees/backport

Then, create a pull request where the base branch is v14-branch and the compare/head branch is backport-520-to-v14-branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants