You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When combine-prs merges dependabot PR's, the target branch ends up with a merge commit for each dependabot branch - so if three dependabot branches get merged, the resulting combined PR has six commits (three of which are merge commits), and then a fourth merge commit happens when the combined branch PR is merged to main:
The merge commits from the dependabot branches to the combined branch don't add a great deal of useful information - is there a way to suppress them in order to reduce the noise in the commit history? Perhaps cherrypicking the commits from the dependabot branches into the combined branch, rather than merging?
The text was updated successfully, but these errors were encountered:
When combine-prs merges dependabot PR's, the target branch ends up with a merge commit for each dependabot branch - so if three dependabot branches get merged, the resulting combined PR has six commits (three of which are merge commits), and then a fourth merge commit happens when the combined branch PR is merged to main:
The merge commits from the dependabot branches to the combined branch don't add a great deal of useful information - is there a way to suppress them in order to reduce the noise in the commit history? Perhaps cherrypicking the commits from the dependabot branches into the combined branch, rather than merging?
The text was updated successfully, but these errors were encountered: