Debug page should not show commits that are part of the git tree from a merge

[warrensplayer]

Description

The Debug page shows runs from Cypress Cloud that match the commit shas from the user's current working environment by performing a git log to find the latest 100 commit shas. If code is merged in from another branch, then both the merge commit that is created as well as other commits from the merged in branch will show in the commit log. This could cause the Debug page to show a run that does not relate to the user's current code that is checked out.

Example:

user has branched from develop with one commit

A -- B   <-develop
       \
        C   <-*feature

If the user is on feature branch and does a git log, then the out put would be: C,B,A

another commit on develop is merged to feature

A -- B ---- D ---  <-develop
       \          \ 
        C -------- E    <-*feature

After merging in develop and creating the merge commit of E, a git log would output: E, D, C, B, A

For the purpose of the Debug page, the user would not want to see any runs associated with the D commit since it did not occur on the feature branch.

Expected behavior

In GitDataSource, the --first-parent option should be added to the git log command to make sure that only commits from the first parent in the git history will be returned in the log command. For the above scenario, that should return: E, C, B, A

Also, make sure to add a test case to to the unit tests to check for this situation.

[warrensplayer]

Hey team! Please add your planning poker estimate with Zenhub @astone123 @jordanpowell88 @lmiller1990 @marktnoonan @mike-plummer

[cypress-bot]

Released in 12.9.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v12.9.0, please open a new issue.