@robin Hope you could review this PR.

Thanks for working on this. Will review over the weekend.

I did some basic testing and it is throwing exception. To reproduce:

1. Push this test repository to a project
2. Switch to commit "Add main1.txt" and cherry pick it to dev branch

Additional observations:

1. Label of the dialog selecting branch should be "Cherry Pick Commit" instead of "Revert Commit"
2. No space between branch selector and commit message input.

If I revert commit to any branch, it will report exception. Also if the commit being cherry-picked to a branch with conflict modification, there are exceptions.

Please do more testing before requesting review to save our time.

Also I checked the code briefly:

1. An integer is used to distinguish cherrypick/revert. This makes code less readable, a boolean or enum can be better
2. Only commit signature is checked for branch protection. Please do the same as in pull request update source feature to check other rules

Sorry for causing the trouble. I will go through all functions and perform more tests to save our time.

No problem. If you are unsure about some functionalities, just raise them in the pull request.

No problem. If you are unsure about some functionalities, just raise them in the pull request.

@robin

1. I wonder whether it is necessary to check the commit is obsolete since when cherry pick in some situations, calling the commit function will produce "Commit is obsolete".
2. If the commit being cherry-picked to a branch with conflict modification, exceptions are fixed and now an error is displayed. I don't know if this is appropriate.

The correct workflow would be:

1. Display a dialog to let user select target branch.
2. Get head commit of target branch, and check if there is a conflict when cherry-pick/revert a new commit onto the branch. If yes, display error and exit
3. Continue to check branch protection rules, and there are any violations, display error and exit
4. Continue to display commit message for user to customize (the default commit message should be the one git uses when cherry-pick/revert from command line)
5. Check if customized commit message satisfies branch protection commit message requirement.
6. Now cherry-pick/revert the commit onto target branch, with old commit and parent commit set to head commit retrieved in step 2. This ensures that the branch can be safely updated without overriding others. In case the branch is updated after step 2, the commit method will throw obsolete commit exception which is fine.

@robin I have reworked on this pr and changed the realization of cherry pick and revert. Wish you could review it and give some advice.

Large part of the logic works great now. I will merge and continue to make some improvements at my side.