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

Branch name escape problem #25865

Closed
yp05327 opened this issue Jul 13, 2023 · 4 comments · Fixed by #25875
Closed

Branch name escape problem #25865

yp05327 opened this issue Jul 13, 2023 · 4 comments · Fixed by #25875
Labels

Comments

@yp05327
Copy link
Contributor

yp05327 commented Jul 13, 2023

Description

Related: #25830

Gitea Version

latest

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

build

Database

None

@puni9869
Copy link
Member

Thanks for summarizing it in short.
You are correct about Github.

@silverwind
Copy link
Member

I don't get it. What is wrong on https://try.gitea.io/yp05327/testrepo/src/branch/test%2311?

@puni9869
Copy link
Member

Thats the correct url for test#11 branch. Nothing wrong with it.

@yp05327
Copy link
Contributor Author

yp05327 commented Jul 20, 2023

I don't get it. What is wrong on https://try.gitea.io/yp05327/testrepo/src/branch/test%2311?

After access this link, you can select this branch again in the selector.
Then the url will become https://try.gitea.io/yp05327/testrepo/src/branch/test#11

GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Jul 25, 2023
lunny pushed a commit that referenced this issue Jul 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 5, 2023
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants