-
answer should be cherry-pick C3 C5 C7, solution shows C3 C4 C7
-
**Describe the bug**
When backporting a PR that was merged with the "squash and merge" method, and the backporting fails (due to conflicts), the suggestion message doesn't work, because it does not…
-
-
Note: The cherry-pick bot failed to create this backport. See https://github.com/konveyor/tackle2-ui/actions/runs/9289091416/job/25562122346#step:4:20.
```
Run BRANCH_NAME="cherry-pick-pr1926-rel…
sjd78 updated
1 month ago
-
https://github.com/RedisLabsModules/RSCoordinator/pull/63
https://github.com/RedisLabsModules/RSCoordinator/pull/61
-
## 🚀 Feature
In this RFC, we propose the policy aiming to guide the decision-making process for determining whether Pull Requests (PRs) should be cherry-picked onto a release branch after the relea…
-
Now we can use `hack/chery_pick_pull.sh` script in kubeedge/kubeedge repo to auto cherry pick the patch to release branch, it's need to write some docs to guide developer use this script.
-
### Description
In v1.21.7 cherry picking commit hangs forever. The logs are:
```
2024/03/05 10:51:57 ...eb/routing/logger.go:102:func1() [I] router: completed GET /LersUchet/LersUchet/_cherrypic…
-
### Description
When we cherry-pick a (non-merge) commit in `git` there's no relation between the original branch, it just copies over the commit and re-applies on current HEAD. For this reason the…
-
With magit, when hitting `A` with a commit in the log at point, the top suggestion (before any branches) is the focused commit:
![image](https://user-images.githubusercontent.com/625793/118684299-6…