• ikidd@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    8
    ·
    4 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.

    • tofuOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      4 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)

        • tofuOP
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          1
          ·
          3 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.

          • corsicanguppy@lemmy.ca
            link
            fedilink
            English
            arrow-up
            1
            ·
            29 minutes ago

            I’m non-container - too much time in security - but that’s a wicked workflow. Well done.