• ikidd@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    8
    ·
    10 hours ago

    Might pay to wait a minor or two before repinning your compose file, Forgejo has had issues on the first release of a major.

    • tofu@lemmy.nocturnal.gardenOP
      link
      fedilink
      English
      arrow-up
      8
      ·
      10 hours ago

      Generally, yes! I couldn’t resist though and merged the renovate PR - seems fine so far. (It’s my local single user instance and I could easily restore, so it hasn’t been particularly high stakes)

        • tofu@lemmy.nocturnal.gardenOP
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          10 hours ago

          Yeah, I keep forgejo’s compose file in forgejo. Changing the file triggers my Komodo which pulls the new file and applies it. It may interrupt a pipeline triggered by the merge or similar, but it’s generally fine.

            • Victor@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              5 hours ago

              too much time in security

              By this, do you mean there’s a lot of work with security when running in a container?