Seems like there may be an api difference, their api is documented at https://gitee.com/api/v5/swagger
During the configuration the url gitee.com and their standard token passes the check.
I get the following in the console window:
gitea-mirror | Importing repo: REDACTED to owner: REDACTED
gitea-mirror | [Org Creation] Validating user authentication before organization operations
gitea-mirror | [Org Creation] Authenticated as user: REDACTED (ID: REDACTED )
gitea-mirror | [Org Creation] Attempting to get or create organization: REDACTED (attempt 1/3)
gitea-mirror | [Org Creation] Organization REDACTED already exists with ID: REDACTED
gitea-mirror | Mirroring repository REDACTED /REDACTED to organization REDACTED as REDACTED
gitea-mirror | Error while mirroring repository REDACTED : HTTP 405: 405 Not Allowed
I wonder if it might be an issue with the organization, I tried to find a setting to force all repos into the user path, but it seems like no matter what it tries to use the org.
Originally created by @jdewe34h45g3 on GitHub (Jun 21, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/330
Originally assigned to: @arunavo4 on GitHub.
Seems like there may be an api difference, their api is documented at https://gitee.com/api/v5/swagger
During the configuration the url gitee.com and their standard token passes the check.
I get the following in the console window:
gitea-mirror | Importing repo: REDACTED to owner: REDACTED
gitea-mirror | [Org Creation] Validating user authentication before organization operations
gitea-mirror | [Org Creation] Authenticated as user: REDACTED (ID: REDACTED )
gitea-mirror | [Org Creation] Attempting to get or create organization: REDACTED (attempt 1/3)
gitea-mirror | [Org Creation] Organization REDACTED already exists with ID: REDACTED
gitea-mirror | Mirroring repository REDACTED /REDACTED to organization REDACTED as REDACTED
gitea-mirror | Error while mirroring repository REDACTED : HTTP 405: 405 Not Allowed
I wonder if it might be an issue with the organization, I tried to find a setting to force all repos into the user path, but it seems like no matter what it tries to use the org.
@jdewe34h45g3 Gitee's API diverges too much from Gitea's to support without significant dedicated effort. The POST /repos/migrate endpoint we rely on for mirroring doesn't exist on Gitee (returns 405), and org creation paths also differ. This isn't a quick config fix.
Gitea Mirror is scoped to Gitea-compatible instances, so closing this for now. A Gitee-specific fork would be the right path if there's enough community interest.
<!-- gh-comment-id:4765609158 -->
@arunavo4 commented on GitHub (Jun 22, 2026):
@jdewe34h45g3 Gitee's API diverges too much from Gitea's to support without significant dedicated effort. The `POST /repos/migrate` endpoint we rely on for mirroring doesn't exist on Gitee (returns 405), and org creation paths also differ. This isn't a quick config fix.
Gitea Mirror is scoped to Gitea-compatible instances, so closing this for now. A Gitee-specific fork would be the right path if there's enough community interest.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jdewe34h45g3 on GitHub (Jun 21, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/330
Originally assigned to: @arunavo4 on GitHub.
Seems like there may be an api difference, their api is documented at https://gitee.com/api/v5/swagger
During the configuration the url gitee.com and their standard token passes the check.
I get the following in the console window:
gitea-mirror | Importing repo: REDACTED to owner: REDACTED
gitea-mirror | [Org Creation] Validating user authentication before organization operations
gitea-mirror | [Org Creation] Authenticated as user: REDACTED (ID: REDACTED )
gitea-mirror | [Org Creation] Attempting to get or create organization: REDACTED (attempt 1/3)
gitea-mirror | [Org Creation] Organization REDACTED already exists with ID: REDACTED
gitea-mirror | Mirroring repository REDACTED /REDACTED to organization REDACTED as REDACTED
gitea-mirror | Error while mirroring repository REDACTED : HTTP 405: 405 Not Allowed
I wonder if it might be an issue with the organization, I tried to find a setting to force all repos into the user path, but it seems like no matter what it tries to use the org.
@arunavo4 commented on GitHub (Jun 22, 2026):
@jdewe34h45g3 Gitee's API diverges too much from Gitea's to support without significant dedicated effort. The
POST /repos/migrateendpoint we rely on for mirroring doesn't exist on Gitee (returns 405), and org creation paths also differ. This isn't a quick config fix.Gitea Mirror is scoped to Gitea-compatible instances, so closing this for now. A Gitee-specific fork would be the right path if there's enough community interest.