🚀 Introducing Quarto Extensions Updater!

A GitHub Action that brings Dependabot-style automation to your Quarto extensions.

✨ Auto-detection
📦 Smart updates
🤖 Auto-merge support

Set it and forget it (or almost).

https://mickael.canouil.fr/posts/2025-12-12-quarto-extensions-updater/

#Quarto #GitHubActions #Automation

Quarto Extensions Updater: Automating Extension Maintenance with GitHub Actions – MCU

Discover how to automate Quarto extension updates in your repositories using a Dependabot-style GitHub Action that keeps your extensions current with zero manual effort.

MCU

Days since running into the Python 3.1 problem: 0

> The version '3.1' with architecture 'x64' was not found for Ubuntu 22.04.
The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

https://hugovk.dev/blog/2021/the-python-3-1-problem/
#Python #YAML #GitHubActions

New on  
"How to Publish a Java Maven Project to Maven Central using JReleaser and GitHub Actions (2025 Guide)" by Jago de Vreede.

A practical guide for Java Developers, this tutorial demystifies publishing your Java Maven project to Maven Central with JReleaser and GitHub Actions.

https://foojay.io/today/how-to-publish-a-java-maven-project-to-maven-central-using-jreleaser-and-github-actions-2025-guide/

#Java #Maven #GitHubActions #JReleaser

How to Release a Java Module to Maven Central with JReleaser and GitHub Actions (2025 Guide)

Complete step-by-step guide to publishing Java modules to Maven Central using JReleaser and GitHub Actions. Learn GPG signing, automation, and CI/CD best practices for Maven releases in 2025.

foojay

GitHub Actions biến việc deploy thành tự động, giảm stress cuối tuần. Từ file YAML đơn giản tới pipeline đa môi trường, cache và bảo mật secrets. 73% dev thấy tần suất deploy tăng, nhưng cần tối ưu tốc độ. Hãy bắt đầu xây pipeline ngay! #GitHubActions #CI/CD #DevOps #Automation #LậpTrình #PhátTriểnPhầnMềm

https://dev.to/tavernetech/github-actions-from-yaml-hell-to-pipeline-heaven-4hcm

GitHub Actions: From YAML Hell to Pipeline Heaven 🔧

Master GitHub CI/CD with practical examples, advanced tips, and lessons learned from 20+ years in the trenches.

DEV Community

BibInject là công cụ kết hợp HTML + BibTeX thành HTML có tham khảo (hỗ trợ GitHub Actions). Tính năng nổi bật: hệ thống chèn HTML, giao diện web, pipeline GitHub Actions, parser BibTeX bằng Python, không cần cài đặt. Mở nguồn, miễn phí và chào mừng cộng đồng tham gia! #BibInject #GitHubActions #LaTeX #CôngNghệ #OpenSource #ĐóngGóp

https://youtu.be/_Y-NQ0-TpJ4

BibInject Demonstration

YouTube

Cải tiến ứng dụng Flutter hàng ngày qua Hive, tái tạo luồng, thẻ lỗi & GitHub Actions! 🚀
Tối ưu cache dữ liệu, xử lý lỗi trực quan, tự động hóa kiểm thử. Tham khảo tuyệt vời cho các nhà phát triển #Flutter #AppDev #Coding #Hive #GitHubActions #CôngNghệ #PhátTriểnMởRộng

https://www.reddit.com/r/programming/comments/1pi7i3k/improving_my_flutter_dailyrecap_app_via_hive/

GitHub Actions Has a Package Manager, and It Might Be the Worst

GitHub Actions has a package manager that ignores decades of supply chain security best practices: no lockfile, no integrity verification, no transitive pinning

Andrew Nesbitt

This last round of cancellations was due to a funny interaction between ancient Meson (0.62, which I get from Ubuntu 22.04's repos) and new Clang (21.4, built from source in that workflow). So my newest (hopefully last, for now) change is to download the newest Meson and use that instead of system Meson.

Oh and I need Ubuntu 22.04 because I wanna compile against an old enough glibc to make the software usable on more distros. I hate glibc so much T_T

#linux #githubactions #ci #programming

×

Day 3: GitHub Actions with r-lib/actions - CI/CD Setup 🚀

Automate your package testing across multiple platforms and R versions! 🔄
Quick setup: ⚡

💡 Pro Tip: The standard check runs on Windows, macOS, and Ubuntu with
multiple R versions.

📚 Resources: https://github.com/r-lib/actions

#GitHubActions #rstats #CI #RPackageAdvent2025

1/ The Trust Problem: You write a package on your Mac. A user on Windows tries it - it breaks. Another on Linux - different error. You can't test everywhere. Users lose trust. You lose sleep debugging platform-specific issues.
2/ The Manual Testing Nightmare: Before CI/CD, "testing across platforms" meant:
Begging friends with Windows machines
Spinning up VMs (if you knew how)
Hoping rhub worked
Crossing fingers for CRAN
Fixing bugs AFTER users found them
3/ Enter GitHub Actions: Every push, every pull request - your package gets tested on:
Windows (latest R, oldrel, devel)
macOS (multiple versions)
Ubuntu (multiple versions) Automatically. For free. While you sleep.

4/ One Command Setup:
usethis::use_github_action("check-standard")

That's it. You now have professional-grade CI that most companies pay thousands for. Your package is tested like tidyverse packages.

5/ What Actually Happens: When you push code:
GH Actions spins up 3+ machines
Installs R on each
Installs your dependencies
Runs R CMD check
Reports results back
All in ~5-10 minutes
You get a ✅ or ❌ immediately.
6/ Real Example: Last month I added a function using tempdir(). Worked perfectly on my Mac. GitHub Actions caught that it failed on Windows due to path separators. Found in 8 minutes, not 8 days post-CRAN submission.

7/ The Three Essential Actions:
usethis::use_github_action("check-standard") # Core testing
usethis::use_github_action("test-coverage") # Track coverage
usethis::use_github_action("pkgdown") # Auto-deploy docs

These three give you: testing, metrics, and documentation. Professional package development.

8/ Coverage Tracking: The test-coverage action pushes to https://codecov.io, giving you a badge showing % of code tested. This isn't vanity - it identifies untested functions that need attention. Public accountability drives quality.
Codecov: Code Coverage Testing & Insights Solution

Ship high-quality code & spend less time debugging. Improve developer workflow, re-run flaky tests, & track JavaScript bundle size. Learn about our code quality & coverage tool here.

Codecov
9/ Documentation Automation: The pkgdown action rebuilds your website on every push. Docs are ALWAYS current. No "oops, forgot to rebuild the site." Users always see up-to-date documentation. Zero extra work.
10/ The Confidence Factor: Before pushing to CRAN, you KNOW your package works everywhere. That ✅ on your commits means:
No platform-specific bugs
Tests pass on all versions
Documentation builds
Coverage is tracked
CRAN submission becomes routine, not stressful.
11/ The Bottom Line: GitHub Actions transforms package development from "hope it works" to "know it works." It's like having a QA team that works 24/7, for free, testing every change. This is how professionals develop packages.
@Drmowinckels these threads are very good. I have some reading to do.
@nxskok really happy you are enjoying them!