Skip to content
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

Closed
1 of 3 tasks
bluecatchbird opened this issue Oct 22, 2019 · 7 comments

Comments

@bluecatchbird
Copy link

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

Screenshot_2019-10-22 blubb

@guillep2k
Copy link
Member

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

@zeripath
Copy link
Contributor

zeripath commented Oct 22, 2019

I think this is describing a situation whereby there is actually no conflict but Gitea incorrectly thinks there is.

@bluecatchbird
Copy link
Author

@zeripath you are right! there is no conflict, but gitea shows one.

@stale
Copy link

stale bot commented Dec 22, 2019

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.

@stale stale bot added the issue/stale label Dec 22, 2019
@zeripath
Copy link
Contributor

Heya could you test again on master I think we may have inadvertently resolved this.

@stale stale bot removed the issue/stale label Dec 22, 2019
@stale
Copy link

stale bot commented Feb 20, 2020

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.

@stale stale bot added the issue/stale label Feb 20, 2020
@stale
Copy link

stale bot commented Mar 5, 2020

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Mar 5, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants