Closed simonswine closed 1 week ago
This PR must be merged before a backport PR will be created.
This PR must be merged before a backport PR will be created.
The backport to release/v1.6
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-3365-to-release/v1.6 origin/release/v1.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x fd207b19b46dfe03a0466a8238639958bfa8eeab
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-3365-to-release/v1.6
# Create the PR on GitHub
gh pr create --title '[release/v1.6] Update golang version to 1.21.11' --body 'Backport fd207b19b46dfe03a0466a8238639958bfa8eeab from #3365' --label 'type/bug' --label 'backport' --base release/v1.6 --milestone release/v1.6 --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-3365-to-release/v1.6
# Create a pull request where the `base` branch is `release/v1.6` and the `compare`/`head` branch is `backport-3365-to-release/v1.6`.
# Remove the local backport branch
git switch main
git branch -D backport-3365-to-release/v1.6
Hello @simonswine! Backport pull requests need to be either:
Please, if the current pull request addresses a bug fix, label it with the
type/bug
label. If it already has the product approval, please add theproduct-approved
label. For docs changes, please add thetype/docs
label. If the pull request modifies CI behaviour, please add thetype/ci
label. If none of the above applies, please consider removing the backport label and target the next major/minor release. Thanks!