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.

Sign up for GitHub

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

Jump to bottom

Fix path cleanup in multiple places (#3871) #3873

Merged
merged 1 commit into from
May 1, 2018
Merged

Fix path cleanup in multiple places (#3871) #3873

merged 1 commit into from
May 1, 2018

Conversation

lafriks
Copy link
Member

@lafriks lafriks commented May 1, 2018

Backport #3871

@lafriks lafriks added type/bug topic/security Something leaks user information or is otherwise vulnerable. Should be fixed! labels May 1, 2018
@lafriks lafriks added this to the 1.4.1 milestone May 1, 2018
@bkcsoft bkcsoft added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label May 1, 2018
@thehowl
Copy link
Contributor

thehowl commented May 1, 2018

LGTM

@bkcsoft bkcsoft added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels May 1, 2018
@appleboy appleboy merged commit 15cdb19 into go-gitea:release/v1.4 May 1, 2018
@lafriks lafriks deleted the fix/backport_path_cleanup branch May 1, 2018 09:25
@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.
Reviewers

@appleboy appleboy appleboy approved these changes

Assignees
No one assigned
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. topic/security Something leaks user information or is otherwise vulnerable. Should be fixed! type/bug
Projects
None yet
Milestone
1.4.1
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@lafriks @thehowl @appleboy @bkcsoft