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 Ryu-Cho attempts to create a PR, but a merge conflict exists, it only logs a message to the console that tells the user to create the PR themselves. This message is hidden for the most part when dealing with GitHub Actions logs, leaving the user wondering why a PR was not created.
I think it would be more user friendly for Ryu-Cho to:
comment on the associated issue that a merge conflict exists
if possible, submit a PR anyway, where GitHub would automatically indicate a merge conflict
enable configuration of this behavior
The text was updated successfully, but these errors were encountered:
tony19
changed the title
[feature request] Configure merge-conflict handling
[feature request] Improve merge-conflict handling
Jul 22, 2022
When Ryu-Cho attempts to create a PR, but a merge conflict exists, it only logs a message to the console that tells the user to create the PR themselves. This message is hidden for the most part when dealing with GitHub Actions logs, leaving the user wondering why a PR was not created.
I think it would be more user friendly for Ryu-Cho to:
The text was updated successfully, but these errors were encountered: