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

Tag with "/" in name blocks pushing of tag with similar name #7985

Closed
2 of 7 tasks
j123b567 opened this issue Aug 26, 2019 · 4 comments · Fixed by #8074
Closed
2 of 7 tasks

Tag with "/" in name blocks pushing of tag with similar name #7985

j123b567 opened this issue Aug 26, 2019 · 4 comments · Fixed by #8074
Labels
Milestone

Comments

@j123b567
Copy link
Contributor

Description

If the repository has tag e.g. a/v1 and also tag v1, then the later one cause problems with gitea. For git itself, it is completely valid scenerio.

Gitea receives the tag but reports

remote: Gitea: Internal Server Error
remote: Failed to Update: tagtest/tagtest1 Branch: v1 Error: PushUpdateAddTag: GetTag: object does not exist [id: v1, rel_path: ]

Tag is later not shown in releases but can be directly accessed by typing correct URL
for tag a/v1 https://try.gitea.io/tagtest/tagtest1/src/tag/a/v1
for tag v1 https://try.gitea.io/tagtest/tagtest1/src/tag/v1

Steps to reproduce

mkdir test
cd test
git init
git commit -m a
git tag a/v1
git tag v1
git remote add origin https://try.gitea.io/tagtest/tagtest2.git
git push -u origin master
git push --tags

This cause an error and tag v1 is not visible in the UI but it should be.

@j123b567
Copy link
Contributor Author

Possibly related to #7945

@j123b567
Copy link
Contributor Author

After investigation, it is duplicate, so closing it.

@j123b567
Copy link
Contributor Author

I must reopen the issue, because it was not duplicate. PR #7990 is wrong solution and issue #7945 is closed.

@richmahn
Copy link
Contributor

richmahn commented Sep 4, 2019

Good catch. Yeah, the other issue was dealing with a branch with a similar name. Glad @guillep2k made a good fix for this.

@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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants