How can I track which commits were already merged using Cherry pick

0
After migrating our Mendix project from SVN to Git, the old Port Fix was replaced with Cherry Pick. When we were still on SVN, it was very easy to see which commits from a feature branch were already merged into the main line — Mendix visually marked the merged commit in the history as disabled, so we could immediately recognize it. Since switching to Git: Cherry pick does not visually indicate which commits were already merged Revision IDs are now random hashes, making it extremely hard to track what was already applied There is no disabled row or any other visual marker like before Studio Pro does not clearly map commit history between branches What is the recommended workflow in Git-based Mendix projects to track which commits were already merged into the main line? How do you determine what still needs to be cherry picked versus what is already included?   Any best practices or guidance would be greatly appreciated.
asked
1 answers
0

Thank you for your question. You may also be interested in this thread, also about merge UX issues in Git compared to SVN.

 

The signals are clear that there is a need for a better cherry-picking experience (in bulk, and showing which ones were already picked), and we are considering how to approach this, but have not yet planned anything concrete.

As PM I'll follow this thread to see what further discussion arises.

answered