github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 21:10:00 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Rest API, doesnt show releases of Migrated Repository #3009

New Issue
Closed
opened 2025-11-02 04:57:11 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 04:57:11 -06:00
Owner
Copy Link

Originally created by @wlauppe on GitHub (Mar 6, 2019).

  • Gitea version (or commit ref):1.7.3
  • Git version: 2.11.0
  • Operating system:debian stretch
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

If I create a repository via the migration tool releases dont show up in the rest response.

Steps to reproduce:
click on "+" "new migration"
enter https://github.com/go-gitea/gitea into "clone url"

query the rest interface via bash (or swagger)

token=xxx
usern=xxx
server=server .name

curl -X GET "https://$server/api/v1/repos/$user/gitea/releases?access_token=$token" -H "accept: application/json"

No migrated releases are shown, if you create a new release in this this repository the rest api returns a result, but the migrated ones are still missing.

Screenshots

Originally created by @wlauppe on GitHub (Mar 6, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref):1.7.3 - Git version: 2.11.0 - Operating system:debian stretch - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description If I create a repository via the migration tool releases dont show up in the rest response. Steps to reproduce: click on "+" "new migration" enter https://github.com/go-gitea/gitea into "clone url" query the rest interface via bash (or swagger) token=xxx usern=xxx server=server .name curl -X GET "https://$server/api/v1/repos/$user/gitea/releases?access_token=$token" -H "accept: application/json" No migrated releases are shown, if you create a new release in this this repository the rest api returns a result, but the migrated ones are still missing. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror commented 2025-11-02 04:57:12 -06:00
Author
Owner
Copy Link

@wlauppe commented on GitHub (Mar 6, 2019):

releases

hiere is a screenshot, the newly entered release "test" is shown in the api, the migrated ones are not.

@wlauppe commented on GitHub (Mar 6, 2019): ![releases](https://user-images.githubusercontent.com/3273201/53899846-68fa6800-403b-11e9-81f6-6676aedf9af9.png) hiere is a screenshot, the newly entered release "test" is shown in the api, the migrated ones are not.
GiteaMirror commented 2025-11-02 04:57:12 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Mar 6, 2019):

There is a difference between releases and tags. Note in your screenshot how the new release you created looks different from the imported tags.

@techknowlogick commented on GitHub (Mar 6, 2019): There is a difference between releases and tags. Note in your screenshot how the new release you created looks different from the imported tags.
GiteaMirror commented 2025-11-02 04:57:13 -06:00
Author
Owner
Copy Link

@wlauppe commented on GitHub (Mar 6, 2019):

ah ok, thats confusing, but the migrated repository still lists 53 releases, so they must have been imported? or not?
releases2

@wlauppe commented on GitHub (Mar 6, 2019): ah ok, thats confusing, but the migrated repository still lists 53 releases, so they must have been imported? or not? ![releases2](https://user-images.githubusercontent.com/3273201/53900742-7a447400-403d-11e9-903c-21b6d4a7b796.png)
GiteaMirror commented 2025-11-02 04:57:13 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Mar 6, 2019):

just like on github the releases tab includes tags as well as releases.

@techknowlogick commented on GitHub (Mar 6, 2019): just like on github the releases tab includes tags as well as releases.
GiteaMirror commented 2025-11-02 04:57:13 -06:00
Author
Owner
Copy Link

@wlauppe commented on GitHub (Mar 7, 2019):

Thanks for the quick reply, so to summerize:
even if counterintuitive at first it works as intended.
Releases are not imported from github only tags are.
Tags can not by queried at the moment by the rest api but will be in the 1.8 release
https://github.com/go-gitea/gitea/issues/2738

@wlauppe commented on GitHub (Mar 7, 2019): Thanks for the quick reply, so to summerize: even if counterintuitive at first it works as intended. Releases are not imported from github only tags are. Tags can not by queried at the moment by the rest api but will be in the 1.8 release https://github.com/go-gitea/gitea/issues/2738
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3009
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?