Release from tag requires target branch, drops tag from Tags page [imported from GitLab]. #602

Open
opened 2 months ago by mschilli · 2 comments

I just signed up to Codeberg.org and started migrating repositories from GitLab.
I noticed releases were not imported so I wanted to re-create them manually. This is when I noticed the tag I wanted to base the release of was missing: The tag itself was pulled. However, the Tags page does not list it.
The only upstream issue I couldfind that seems related is gitea#18715, with a supposed fix in gitea#18719. Im I doing something wrong? Is this a known issue I failed to find? This kind of puts the breaks on me migrating all my precious projects over here. 😉
Thank you in advance for the feedback and for providing an ethical way to manage our beloved projects.

I just signed up to Codeberg.org and started migrating repositories from GitLab. I noticed releases were not imported so I wanted to re-create them manually. This is when I noticed the tag I wanted to base the release of was missing: [The tag itself](https://codeberg.org/mschilli/bamam/src/tag/v0.1) was pulled. However, [the Tags page](https://codeberg.org/mschilli/bamam/tags) does not list it. The only upstream issue I couldfind that seems related is [gitea#18715](https://github.com/go-gitea/gitea/issues/18715), with a supposed fix in [gitea#18719](https://github.com/go-gitea/gitea/pull/18719). Im I doing something wrong? Is this a known issue I failed to find? This kind of puts the breaks on me migrating all my precious projects over here. :wink: Thank you in advance for the feedback and for providing an ethical way to manage our beloved projects.
mschilli changed title from Tag pages does not list (all) tag(s) [imported from GitLab]. to Tags page does not list (all) tag(s) [imported from GitLab]. 2 months ago
Collaborator

Welcome to Codeberg. Yeah, the mentioned PR should be live already, so this is likely a new bug or a missed edge case. We'll have to hunt it down.

What would help: Can you reproduce this issue at https://try.gitea.io and share the link? We can then sent the report upstream to Gitea.

Thank you.

Welcome to Codeberg. Yeah, the mentioned PR should be live already, so this is likely a new bug or a missed edge case. We'll have to hunt it down. What would help: Can you reproduce this issue at https://try.gitea.io and share the link? We can then sent the report upstream to Gitea. Thank you.
fnetX added the
bug
gitea-related
labels 2 months ago
Poster

@fnetX:

Thank you for the fast reponse and the warm welcome.

What would help: Can you reproduce this issue at https://try.gitea.io and share the link? We can then sent the report upstream to Gitea.

I'm not a big fan of using websites that force me to help Google's AI to learn how to recognize motorcycles but alas, it is for a good cause.
However, reproducing this help to better understand what is going on. It turned out to be more complex than I initially realized.
Here is how I successfully recreated the faulty state:

  1. Migrate https://gitlab.com/mschilli/bamam.git.
  2. Navigate to Tags page: Actually, all five tags were listed.
  3. Follow 'New Release' link for v0.1 tag.
  4. Fill 'Title' form field with 'Test'.
  5. Try saving as draft: Fails with error:

    Target cannot be empty.

  6. Tag was pre-filled with correct tag name ('v0.1'), target with 'Target: master'.
  7. Click Target dropdown: Must choose branch name ('master' or 'dev').
  8. Select 'master'.
  9. Save as draft: Draft release page created (incl. link to v0.1 tag pointing to https://try.gitea.io/mschilli/bamam/releases#)
  10. Navigate to Tags tab: v0.1 tag is gone.

edit: Forgot the

...and share the [l]ink?

part... 🤦

Here it is: https://try.gitea.io/mschilli/bamam/tags

@fnetX: Thank you for the fast reponse and the warm welcome. > What would help: Can you reproduce this issue at https://try.gitea.io and share the link? We can then sent the report upstream to Gitea. I'm not a big fan of using websites that force me to help Google's AI to learn how to recognize motorcycles but alas, it is for a good cause. However, reproducing this help to better understand what is going on. It turned out to be more complex than I initially realized. Here is how I successfully recreated the faulty state: 1. Migrate https://gitlab.com/mschilli/bamam.git. 2. Navigate to Tags page: Actually, all five tags were listed. 3. Follow 'New Release' link for `v0.1` tag. 4. Fill 'Title' form field with 'Test'. 5. Try saving as draft: Fails with error: > Target cannot be empty. 6. Tag was pre-filled with correct tag name ('v0.1'), target with 'Target: master'. 7. Click Target dropdown: Must choose branch name ('master' or 'dev'). 8. Select 'master'. 9. Save as draft: Draft release page created (incl. link to `v0.1` tag pointing to https://try.gitea.io/mschilli/bamam/releases#) 10. Navigate to Tags tab: `v0.1` tag is gone. --- *edit*: Forgot the > ...and share the [l]ink? part... 🤦 Here it is: https://try.gitea.io/mschilli/bamam/tags
mschilli changed title from Tags page does not list (all) tag(s) [imported from GitLab]. to Release from tag requires target branch, drops tag from Tags pages [imported from GitLab]. 2 months ago
mschilli changed title from Release from tag requires target branch, drops tag from Tags pages [imported from GitLab]. to Release from tag requires target branch, drops tag from Tags page [imported from GitLab]. 2 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.