Codeberg/Community
54
325
Fork
You've already forked Community
12

Strange behavior with tags on a repo migrated from Github #1970

Open
opened 2025年05月31日 22:44:34 +02:00 by soulstenance · 0 comments

Comment

So I migrated one of my repos from Github instead of pushing from local since I wanted to migrate the issues and pull requests as well, and I noticed something strange. Unlike my other repos which I pushed normally, the tags in this repo don't show the description like they do on Github or when running git show [tag] locally. I know the tags are not damaged because the signatures still pass and I can git clone the repo and see that the description is indeed present. It's not a big deal and it seems everything is in order, I'm just baffled why it displays differently.

Here is a repo called kulr I pushed from local. As you can see the tag description is there both in my local repo and on Codeberg.
https://codeberg.org/soulstenance/kulr/releases/tag/v1.0

gitkulr.png

And here is the migrated repo. You can see that both on local and Github, the tag description is shown, but not on Codeberg. (On Github you do have to click the little 3 dots to expand as tags with releases don't show the tag description once clicked on.)
https://github.com/soulstenance/spgu/tags
https://codeberg.org/soulstenance/spgu/releases/tag/v0.1.1

gitspgu.png

Hoping someone can shed some light on this but again, it isn't urgent. I don't know if force pushing the tags from local would solve anything or if I should just leave well enough alone.

### Comment So I migrated one of my repos from Github instead of pushing from local since I wanted to migrate the issues and pull requests as well, and I noticed something strange. Unlike my other repos which I pushed normally, the tags in this repo don't show the description like they do on Github or when running `git show [tag]` locally. I know the tags are not damaged because the signatures still pass and I can git clone the repo and see that the description is indeed present. It's not a big deal and it seems everything is in order, I'm just baffled why it displays differently. Here is a repo called kulr I pushed from local. As you can see the tag description is there both in my local repo and on Codeberg. [https://codeberg.org/soulstenance/kulr/releases/tag/v1.0](https://codeberg.org/soulstenance/kulr/releases/tag/v1.0) ![gitkulr.png](/attachments/b2e1719e-ddcf-413e-9636-fdecba8b04d2) And here is the migrated repo. You can see that both on local and Github, the tag description is shown, but not on Codeberg. (On Github you do have to click the little 3 dots to expand as tags with releases don't show the tag description once clicked on.) [https://github.com/soulstenance/spgu/tags](https://github.com/soulstenance/spgu/tags) [https://codeberg.org/soulstenance/spgu/releases/tag/v0.1.1](https://codeberg.org/soulstenance/spgu/releases/tag/v0.1.1) ![gitspgu.png](/attachments/8126f4a8-91d0-4cb7-b304-d933bac5119e) Hoping someone can shed some light on this but again, it isn't urgent. I don't know if force pushing the tags from local would solve anything or if I should just leave well enough alone.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1970
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?