Post by @Federation_Bot

RE: https://mastodon.social/@ryanprior/117418421130935517

Success! My #Codeberg #CI is set up to run tests for one of my #Fennel projects.

My favorite aspect of this setup is that it uses #xc to run the exact steps documented in my README. This makes the validated setup & testing instructions more discoverable than if they were hidden in a CI config file.

I wrote more about the approach on my blog: https://www.ryanprior.com/posts/put-your-runbook-in-your-readme/

        Put Your Runbook in Your README :: Ryan Prior  — dot com

During software development and maintenance we use an array of commands to build, test, deploy and release our software. When nobody writes these commands down, they're tacit knowledge: the floor-level of computing know-how that's necessary to contribute to the project. This is widely acknowledged as a barrier to entry and an accessibility pain point for Free software. Tacit knowledge of development workflows can also lead to confusion and unnecessary friction between maintainers of a multi-user repository who develop slightly different versions. This is a key aspect of the famous "It Works On My Machine" development methodology.

DNA schedule

@ryanprior@mastodon.social 2 wk. ago

I gave myself a goal for today of getting CI/CD set up in @Codeberg for one of my simpler projects. They approved my application for CI access yesterday, so I should be set.

Reading their docs, the primary CI is Woodpecker, which is being authored by Claude.

Their newer integrated CI system, available "in open alpha," is based on nektos/act, which is also being authored by Claude.

Anybody have CI recommendations? Or know what's going on at Codeberg?

#CI #neverslop #codeberg

#xc #fennel #codeberg #ci

1 Boost

0 Likes

No replies yet

Be the first to share your thoughts.