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

Backport v1.9 - Fixes #7492 - Fixes for DeleteFilePost function to work properly #7489

Conversation

richmahn
Copy link
Contributor

@richmahn richmahn commented Jul 16, 2019

Fixes #7492, backport for v1.9 from these fixes in PR #7478 for v1.10

Found that you could never get an error message when deleting a file as then it would try to use the edit file page template and that would throw errors. Also it had the wrong comparison sign for when looking to see if you can commit to the existing branch when you really want to make a new branch.F

@richmahn richmahn changed the title Fixes for DeleteFilePost function to work properly Backport to v1.9 - Fixes for DeleteFilePost function to work properly Jul 16, 2019
@richmahn richmahn changed the title Backport to v1.9 - Fixes for DeleteFilePost function to work properly Backport v1.9 - Fixes #7492 - Fixes for DeleteFilePost function to work properly Jul 16, 2019
@lafriks lafriks added this to the 1.9.0 milestone Jul 16, 2019
@mrsdizzie
Copy link
Member

This could maybe be closed and a new PR with the updated/merged commit from master cherry picked to release/v1.9?

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Jul 17, 2019
@richmahn
Copy link
Contributor Author

@mrsdizzie That is possible. That PR has a few other fixes, not as urgent, but if ok with the admin, I think it would be good to get into v1.9 as it is weird how any file commit says when you make a new branch you will start a PR, but it doesn't do that.

@richmahn richmahn closed this Jul 17, 2019
@mrsdizzie
Copy link
Member

Ah OK sorry my mistake I read the description wrong -- I do think that change would be worth 1.9 as that is a bug otherwise, but that would be up to someone else

@richmahn
Copy link
Contributor Author

@mrsdizzie Ok, here it is: #7507

@techknowlogick techknowlogick removed this from the 1.9.0 milestone Jul 17, 2019
@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.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants