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 API for branches with slashes #2096

Merged
merged 1 commit into from
Jul 2, 2017
Merged

Fix API for branches with slashes #2096

merged 1 commit into from
Jul 2, 2017

Conversation

ethantkoenig
Copy link
Member

@ethantkoenig ethantkoenig commented Jul 2, 2017 •
edited
Loading

Fixes #2088. Also add an integration test.

@lafriks
Copy link
Member

lafriks commented Jul 2, 2017

LGTM

@tboerger tboerger added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jul 2, 2017
@lafriks lafriks added modifies/api This PR adds API routes or modifies them type/bug labels Jul 2, 2017
@lunny lunny added this to the 1.2.0 milestone Jul 2, 2017
@lunny
Copy link
Member

lunny commented Jul 2, 2017

LGTM

@tboerger tboerger 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 Jul 2, 2017
@lunny lunny merged commit f99489d into go-gitea:master Jul 2, 2017
@ethantkoenig ethantkoenig deleted the fix/branch_api branch July 2, 2017 17:40
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. modifies/api This PR adds API routes or modifies them type/bug
Projects
None yet
Milestone
1.2.0
Development

Successfully merging this pull request may close these issues.

API: branch names need special handling when containing a /
4 participants
@ethantkoenig @lafriks @lunny @tboerger