New: secrets-detector – scan your PHP project for leaked API keys, tokens, passwords in .env, config & code. CI-ready JSON/Markdown reports Symfony Console CLI Supports ignore/include rules MIT licensed & open for feedback!
It is a very exciting #multicast use case you are driving lcagent with, and I am looking forward to learn more about your experiences with this #CI setup.
Just to be on record: I honestly didn’t expect that even non-YAML code ( @nuke build – yeah, I’m talking to you...) would require just as many fucking never-ending commits. Azure DevOps has proven me wrong. (lol)
The real pain point? No local test run No Run pipeline locally Zero feedback until you PR, merge, and let it rip on main
So yeah, we’re basically testing on the main branch. In production. In 2025. For everything else, there’s: ¯\_(ツ)_/¯
Also, I firmly believe that not only Carthage must be destroyed, but also:
- CI/CD with no local feedback loop - “Works on my machine” excuses _ YAML files that silently break on pasted tabs - And every doc that starts with “just”
And yes — I really thought nuke build would make things better... But after 24 hours of commits, checks, and trial-and-error, I’ve been proven otherwise (and I really wanted to make it work and local debugging is awesome — but it’s useless when the docs are a soggy mess and don’t reflect reality.)
I'm holding the next Radicle CI office hour on Wednesday, May 21, at 16:00 UTC at https://meet.jit.si/RadicleCI (that's about a week from now). I'll be there and can answer questions, and I plan to have a demo of installing Radicle CI.
I'm often annoyed by #CI runners complaining about small things like "you didn't indent that YAML file as the linter likes it" or "You made a typo". It's right in the cause, but wastes way more time than needed.
I'd think that a good tool should find the offending #git commit, create a fixup ready for squashing, and offer to push this right onto my branch (or their branch, or offer to just squash).
Before I go implementing or spec'ing it out: Are there tools that already do this right?
Na początek tego niecodziennego tygodnia link do prostej, ale konkretnej instrukcji, jak wykorzystać narzędzia CI/CD Gitlaba w celu wdrożenia swojej aplikacji (tutaj: napisanej w Javie).
@ar Lol, this is what I would have needed about 5 years ago to work around an issue with #GitLab and #CI.
Back then when you had a project with submodules (or just wanted to "git pull something" from within the CI it wouldn't be possible to do so over SSH. And for some reason it was not possible to pull via HTTPS to clients within that environment, so you basically had to manually edit the .gitsubmodules to relative paths after "git submodule add"-ing (Don't know if it's fixed by now)
Klasycznie artykuły z rodzaju "najlepsze X w roku Y" klikają się bardzo dobrze, ale jeśli mają pomóc, to czemu nie. Tutaj mamy zestawienie popularnych narzędzi CI/CD, które w większości dobrze znacie, ale są też te mniej oczywiste.
When debugging failures in CI in steps that execute a shell snippet, it's harder to do when stdout and stderr aren't interleaved. This leads me to think about this: what would the ideal CI run log output be like, for me? I have some thoughts that I'll write down when I have time, but you, dear reader, what is your answer? Assume anything is possible, don't worry about how much work it'd be.
I wrote up how to add it your workflows so you can start testing free-threaded Python 3.13 and 3.14 with either actions/setup-python or actions/setup-uv.
- Coloured highlights in logging (supports --no-colour) - all matching strategy for paths (default is any) - Built in templates: docs, feature, tests and fixes
Usage:
- Define rules in .forgejo/commit-path-rules.toml - Run via CLI or ForgeJo Action
Fun fact: Ancient relics like Maven happily obey any Java version , but modern, cutting-edge tools. Gradle, AWS Lambda, and more require new releases just to function. Because nothing says progress like mandatory dependencies.
Meanwhile, Kubernetes & Maven sit back, laughing. They do whatever they want. They are independent. Unlike you.
the other #rustlang thingy that's been cooking (and just passed a #ci run) is called #taggart.
it uses #tengri to pop up an interactive table to edit things, namely: the #id3 tags of music releases
its purpose? why, to make it easier to prepare a certain pile of content (that we've accumulated with a friend over the past, what, 6-7 years), for publication in a sovereign #faircamp instance! but none of it's well-tagged and existing interactive mediatag editors are ugh
this is the framework code ripped out of #tek, my #tui#daw. currently, it wrapps #ratatui and provides main loop, generic layout logic, and an #sexpr-based mini-#dsl for describing stuff
(some ci run, not even outputting coverage like it ought to, but i don't feel like debugging that right now - PRs welcome!)