Skip to content

backport "Enforce token on api routes (#4840)" #4905

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
Merged
merged 1 commit into from
Sep 11, 2018
Merged

backport "Enforce token on api routes (#4840)" #4905

merged 1 commit into from
Sep 11, 2018

Conversation

techknowlogick
Copy link
Member

As title - backport #4840 to release/v1.5 branch

cc @beeonthego

@techknowlogick techknowlogick added the topic/security Something leaks user information or is otherwise vulnerable. Should be fixed! label Sep 10, 2018
@techknowlogick techknowlogick added this to the 1.5.2 milestone Sep 10, 2018
@bkcsoft bkcsoft added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Sep 11, 2018
@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 Sep 11, 2018
@techknowlogick techknowlogick merged commit 1a68b39 into go-gitea:release/v1.5 Sep 11, 2018
@techknowlogick techknowlogick deleted the backport-4840 branch September 11, 2018 14:39
@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

@lunny lunny lunny approved these changes

@lafriks lafriks lafriks 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!
Projects
None yet
Milestone
1.5.2
Development

Successfully merging this pull request may close these issues.
4 participants
@techknowlogick @lunny @lafriks @bkcsoft