possible /api/v1/user/repos misbehavior #2732

New Issue

GiteaMirror · 2025-11-02T04:45:54-06:00

GiteaMirror commented

2025-11-02 04:45:54 -06:00

Originally created by @Iced-Sun on GitHub (Jan 10, 2019).

Gitea version (or commit ref): 1.6.3
Git version: 2.17.1
Operating system: ubuntu bionic
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
Log gist:

Description

Drone CI uses /api/v1/user/repos to fetch the user repo info. Upon the first time when a repo is created as a fork, say 'user/repoA' -> 'org/repoA', the API does report the newly created 'user/repoA'. Then:

delete 'user/repoA' ( /api/v1/user/repos do also reflects it);
fork 'org/repoA' to 'user/repoA' again.

Now /api/v1/user/repos never reports 'user/repoA' as a repo belongs to 'user'.

Originally created by @Iced-Sun on GitHub (Jan 10, 2019).  - Gitea version (or commit ref): 1.6.3 - Git version: 2.17.1 - Operating system: ubuntu bionic - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - Log gist: ## Description Drone CI uses ```/api/v1/user/repos``` to fetch the user repo info. Upon the first time when a repo is created as a fork, say 'user/repoA' -> 'org/repoA', the API does report the newly created 'user/repoA'. Then: 1. delete 'user/repoA' ( ```/api/v1/user/repos``` do also reflects it); 2. fork 'org/repoA' to 'user/repoA' again. Now ```/api/v1/user/repos``` never reports 'user/repoA' as a repo belongs to 'user'.

GiteaMirror added the issue/stale issue/needs-feedback labels 2025-11-02 04:45:54 -06:00

GiteaMirror closed this issue

2025-11-02 04:45:54 -06:00

GiteaMirror commented

2025-11-02 04:45:55 -06:00

@stale[bot] commented on GitHub (Mar 11, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 11, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:45:55 -06:00

@lunny commented on GitHub (Mar 11, 2019):

Can you reproduce that on https://try.gitea.io ?

@lunny commented on GitHub (Mar 11, 2019): Can you reproduce that on https://try.gitea.io ?

GiteaMirror commented

2025-11-02 04:45:55 -06:00

@stale[bot] commented on GitHub (May 10, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (May 10, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:45:55 -06:00

@stale[bot] commented on GitHub (May 24, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (May 24, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:13:30 -06:00

[PR #2732] [MERGED] Fix typos in app.ini #16562

Sign in to join this conversation.