Skip to content

Error 500 when updating githooks on mirrored repositories #3696

Closed
@johanhugg

Description

@johanhugg
  • Gitea version (or commit ref): 1.5.0-dev
  • Git version:
  • Operating system: Windows 10 x64
  • 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

Since try.gitea.io isn't working at the time of this writing I couldn't test it. But after looking at the code the issue should exist there too.

When creating a migration, and the repository is a mirror, the code doesn't seem to create the git hook repositories that it expects to find, resulting in a file not found error. Image 1 shows a newly created repository that isn't a mirror. There we can see three folders that contain the three sample hooks that are presented in the Gitea Web GUI (Image 2). A newly created repository that is a mirror, doesn't create these folders (Image 3).

Is this intended? Is there a reason why you shouldn't be able to create git hooks for mirrored repositories?

Screenshots

Image 1

image

Image 2

image

Image 3

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/bug

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions