enable locally runnable CI by CobaltCause · Pull Request #2983 · LemmyNet/lemmy
github.com
And a handful of other things. The commit messages are extremely detailed, so please have a look at those. That said, I'll highlight the main points of the PR here: Currently, Lemmy's CI pi...

Dessalines: :bugs-no:

I'm sure his ideas have advantages and the lemmy devs can be frustrating to work with but he literally showed up yesterday spamming the matrix chat and now this

  • Aceivan [they/them, null/void]
    ·
    1 year ago

    Yeah. The thing was he asked about doing this in the matrix before he put the PR together and was essentially given an unequivocal "no" at that time as well

    I don't think the CI is 100% necessary for local development and I think you can run woodpecker locally if you wanted, but yeah the runtimes are dog slow and there's lots of room for improvement, this guy is just being a jerk about it

    • captcha [any]
      ·
      1 year ago

      Local CI only for CI development. You keep your CI simple and use docker and some sort of build scripts like gnu make to do local development.

      Never heard of woodpecker though. New thing to read up on.

      Edit from woodpecker docs:

      Plugins are Docker images with your script as an entrypoint

      NOW THIS IS PODRACING

      • Aceivan [they/them, null/void]
        ·
        1 year ago

        You can build lemmy just fine locally. I think maybe it just doesn't run the test suite unless you use the CI? So I guess the real question is do you need the test suite in the loop for every build. I can see where it'd be nice but I'm barely even a dev so idk

        • captcha [any]
          ·
          1 year ago

          Test suites should be runnable locally. It encourages people to write tests and check then before submitting a pr. But it makes sense for running it in CI to be first priority on an open source project.