gitea: Migration with pull requests from other gitea instance fails

  • Gitea version (or commit ref): 1.14.0+dev-18-gd453533be
  • Git version: 2.26.2
  • Operating system: docker Alpine Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist: 2020/10/22 13:25:46 …ules/task/migrate.go:64:func1() [E] DeleteRepository: repository does not exist [id: 208, uid: 75, owner_name: , name: ] 2020/10/22 13:25:46 modules/task/task.go:51:handle() [E] Run task failed: error while loading reactions: 403 Forbidden

Description

Migration without pull requests works fine for the same repo. …

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 2
  • Comments: 27 (17 by maintainers)

Most upvoted comments

after #13352 all migrations completed successfully with pull requests. thank you! project settings were not migrated, but im not sure if they should…

There very well maybe another equal entries bug - but this report is simply the permissions problem.

@lakostin can you tell me the url from the source, or send it to me via email if it should not get public?

impossible cause it’s in private network