[Feature] Implement Selective Commit Merging Option

[aTheo]

Currently, when the pull bot creating a Pull Request, all commits associated with the branch are automatically included for merging. However, it would greatly enhance user flexibility and efficiency if there was an option to selectively choose which commits to merge into the target branch.

Proposed Solution:
Introducing a feature where users can toggle/select specific commits within the Pull Request interface would provide greater control over the merging process. This option could streamline the code, especially in cases where certain commits are ready for merging while others require further refinement or testing.

Benefits:

• Allows for more granular control over the merging process.
• Facilitates easier identification and selection of relevant commits.
• Enhances collaboration by enabling contributors to focus on specific changes within a Pull Request.

[Wei He]

Hi @atheo89 thanks for the suggestion. I believe what you are proposing is actually against the best git practice for a software development process. I recommend working on different branches instead of picking commits this way. I can foresee issues of merge conflicts and unstable main branch from cherry-picking commits this way. Additionally, since Pull uses GitHub's REST API, I don't think cherry-picking is natively supported. I recommend using git cherry-pick instead for your given workflow.