Skip to content

Disable custom Git Hooks globally via configuration value #2449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 of 7 tasks
techknowlogick opened this issue Sep 2, 2017 · 0 comments · Fixed by #2450
Closed
5 of 7 tasks

Disable custom Git Hooks globally via configuration value #2449

techknowlogick opened this issue Sep 2, 2017 · 0 comments · Fixed by #2450
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Milestone

Comments

@techknowlogick
Copy link
Member

techknowlogick commented Sep 2, 2017

  • Gitea version (or commit ref): 04ec795
  • Git version: 2.11.0
  • Operating system: macOS 10.12.6
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

As a sysadmin hosting gitea for others I'd like the option to disable custom githooks via configuration value so that even the admin of the site can't enable them for users.

@lafriks lafriks added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Sep 2, 2017
@lafriks lafriks added this to the 1.x.x milestone Sep 2, 2017
@lunny lunny modified the milestones: 1.3.0, 1.x.x Sep 12, 2017
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants