-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to resolve pull request, when a file with a conflict is modified later to the same content as on the destination #8630
Comments
Resolving conflicts through the web interface is not currently supported. Conflicts should be resolved in a local copy and pushed back to your PR. If this is a feature request, it would be cool to have this, of course! But this would be a duplicate of #5158 |
I think this is describing a situation whereby there is actually no conflict but Gitea incorrectly thinks there is. |
@zeripath you are right! there is no conflict, but gitea shows one. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Heya could you test again on master I think we may have inadvertently resolved this. |
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
Description
Its not possible to resolve a pull request, when a file with a conflict is modified later to the same content as on the destination branch.
Screenshots
The text was updated successfully, but these errors were encountered: