[Feature] for doctor framewrok #4683

New Issue

GiteaMirror · 2025-11-02T05:59:22-06:00

GiteaMirror commented

2025-11-02 05:59:22 -06:00

Originally created by @6543 on GitHub (Jan 19, 2020).

let gitea repair hooks based on current binary executing path & app.ini settings ...

Originally created by @6543 on GitHub (Jan 19, 2020). let gitea repair hooks based on current binary executing path & app.ini settings ...

GiteaMirror added the type/proposal label 2025-11-02 05:59:22 -06:00

GiteaMirror closed this issue

2025-11-02 05:59:22 -06:00

GiteaMirror commented

2025-11-02 05:59:24 -06:00

@jolheiser commented on GitHub (Jan 19, 2020):

I think this is what Resynchronize pre-receive, update and post-receive hooks of all repositories. does?

@jolheiser commented on GitHub (Jan 19, 2020): I think this is what `Resynchronize pre-receive, update and post-receive hooks of all repositories.` does?

GiteaMirror commented

2025-11-02 05:59:24 -06:00

@techknowlogick commented on GitHub (Jan 19, 2020):

CLI currently has the following commands which would resynch keys and hooks, maybe doctor would alert user that they would need to run the following?

    gitea admin regenerate hooks
    gitea admin regenerate keys

@techknowlogick commented on GitHub (Jan 19, 2020): CLI currently has the following commands which would resynch keys and hooks, maybe doctor would alert user that they would need to run the following? ``` gitea admin regenerate hooks gitea admin regenerate keys ```

GiteaMirror commented

2025-11-02 05:59:24 -06:00

@guillep2k commented on GitHub (Jan 19, 2020):

I think it would be cool if the doctor performed all of those functions by itself as part of its diagnostics/repair procedure. Unless there's some reason for not doing that, of course. We could add flags like --repair-all in case we don't want some destructive step to run by default.

@guillep2k commented on GitHub (Jan 19, 2020): I think it would be cool if the doctor performed all of those functions by itself as part of its diagnostics/repair procedure. Unless there's some reason for not doing that, of course. We could add flags like `--repair-all` in case we don't want some destructive step to run by default.

GiteaMirror referenced this issue

2025-11-02 13:32:38 -06:00

[PR #4683] [MERGED] Add whitespace handling to PR-comparsion #17462

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#4683