Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Gitea
  3. Gitea Git Hooks disabled

Gitea Git Hooks disabled

Scheduled Pinned Locked Moved Solved Gitea
6 Posts 4 Posters 22.5k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    sfeldkamp
    wrote on last edited by
    #1

    @nebulon said in Gitea - Package Updates:

    Full changelog

    https://github.com/go-gitea/gitea/pull/13058

    This change in 1.13.0 broke my repo by causing my existing git hook to fail. Git Hooks tab is now hidden by default.
    I can't successfully push to origin because the hook fails.

    I updated run/gitea/app.ini manually to restore it by adding

    [custom]
    DISABLE_GIT_HOOKS = false

    However, this is not durable for a restart. I was depending on the Git Hooks feature of Gitea to push to mirror my repository to the GitHub Pages app repo to publish it.

    Is it possible to default this value to true instead in the app? Or otherwise provide a way to toggle it that will be durable across versions and installs?

    girishG fbartelsF 2 Replies Last reply
    0
    • S sfeldkamp

      @nebulon said in Gitea - Package Updates:

      Full changelog

      https://github.com/go-gitea/gitea/pull/13058

      This change in 1.13.0 broke my repo by causing my existing git hook to fail. Git Hooks tab is now hidden by default.
      I can't successfully push to origin because the hook fails.

      I updated run/gitea/app.ini manually to restore it by adding

      [custom]
      DISABLE_GIT_HOOKS = false

      However, this is not durable for a restart. I was depending on the Git Hooks feature of Gitea to push to mirror my repository to the GitHub Pages app repo to publish it.

      Is it possible to default this value to true instead in the app? Or otherwise provide a way to toggle it that will be durable across versions and installs?

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @sfeldkamp You can put that config section in /app/data/app.ini instead and restart the app. Please see https://docs.cloudron.io/apps/gitea/ . At run time, the package will merge the package config with your user config to generate /run/gitea/app.ini

      S 1 Reply Last reply
      0
      • girishG girish

        @sfeldkamp You can put that config section in /app/data/app.ini instead and restart the app. Please see https://docs.cloudron.io/apps/gitea/ . At run time, the package will merge the package config with your user config to generate /run/gitea/app.ini

        S Offline
        S Offline
        sfeldkamp
        wrote on last edited by
        #3

        @girish

        oh, man. My bad for not reading the docs on that one. Thanks for the help. 👍

        1 Reply Last reply
        0
        • S sfeldkamp

          @nebulon said in Gitea - Package Updates:

          Full changelog

          https://github.com/go-gitea/gitea/pull/13058

          This change in 1.13.0 broke my repo by causing my existing git hook to fail. Git Hooks tab is now hidden by default.
          I can't successfully push to origin because the hook fails.

          I updated run/gitea/app.ini manually to restore it by adding

          [custom]
          DISABLE_GIT_HOOKS = false

          However, this is not durable for a restart. I was depending on the Git Hooks feature of Gitea to push to mirror my repository to the GitHub Pages app repo to publish it.

          Is it possible to default this value to true instead in the app? Or otherwise provide a way to toggle it that will be durable across versions and installs?

          fbartelsF Offline
          fbartelsF Offline
          fbartels
          App Dev
          wrote on last edited by
          #4

          @sfeldkamp said in Gitea Git Hooks disabled:

          [custom]
          DISABLE_GIT_HOOKS = false

          you have to put it below [security], though.

          1 Reply Last reply
          0
          • krschuermanK Offline
            krschuermanK Offline
            krschuerman
            wrote on last edited by
            #5

            Is this setting supposed to still work in 1.14.2? I added it to /etc/gitea/app.ini in a previous version and it worked, but with each of the last two updates I installed it no longer works for me.

            app.ini looks like this:
            [security]
            INTERNAL_TOKEN = <snip>
            INSTALL_LOCK = true
            SECRET_KEY = <snip>

            [custom]
            DISABLE_GIT_HOOKS = false

            fbartelsF 1 Reply Last reply
            0
            • krschuermanK krschuerman

              Is this setting supposed to still work in 1.14.2? I added it to /etc/gitea/app.ini in a previous version and it worked, but with each of the last two updates I installed it no longer works for me.

              app.ini looks like this:
              [security]
              INTERNAL_TOKEN = <snip>
              INSTALL_LOCK = true
              SECRET_KEY = <snip>

              [custom]
              DISABLE_GIT_HOOKS = false

              fbartelsF Offline
              fbartelsF Offline
              fbartels
              App Dev
              wrote on last edited by
              #6

              Hi @krschuerman,

              for me this still works, but as already said in my last post here in this thread the setting needs to be placed in the security block.

              [security]
              [..]
              DISABLE_GIT_HOOKS = false
              
              1 Reply Last reply
              2
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search