My little open source project crossed 500 image downloads. Not a lot, but kinda fun given how niche it is. 🎉

https://github.com/clajiness/qbop

#opensource #ruby #rubyprogramming #sinatra #opnsense #qbittorrent #github #githubactions #Docker

GitHub - clajiness/qbop: A tool for maintaining a forwarded port from ProtonVPN, while optionally keeping OPNsense and qBittorrent in sync. The tool offers a simple web UI and API with stats and logging.

A tool for maintaining a forwarded port from ProtonVPN, while optionally keeping OPNsense and qBittorrent in sync. The tool offers a simple web UI and API with stats and logging. - clajiness/qbop

GitHub

GitHub Actions is dropping Intel macOS by November.

(Cirrus dropped it in Dec 2022, CircleCI in June 2024, Travis CI dropped all(!) macOS in April, and Anaconda last week.)

CPython has dropped it to tier 2. What does this mean to you? Not too much; we still support it, produce installers, CI failures block releases.

It means we only test on buildbots and failures must be fixed/reverted within 24h rather than immediately.

https://discuss.python.org/t/dropping-intel-mac-to-tier-2/102100

#Python #CPython #macOS #Intel #GitHubActions

Dropping Intel Mac to Tier 2

Anaconda is dropping Intel macOS tomorrow: Starting August 15, 2025, Anaconda will stop building new packages for Intel Mac computers (osx-64). This change affects users who are currently using Intel Mac packages, whether on actual Intel hardware or Apple Silicon Macs running in emulation mode.

Discussions on Python.org

Tired of juggling env vars in GitHub Actions like a circus clown? 🎪 Static vs dynamic, job-level vs step-level — I break down the best moves to keep your workflows slick and drama-free. No more env var chaos. Your CI deserves better. #GitHubActions #DevOps #CI_CD

https://amedee.be/%f0%9f%a7%aa-github-actions-and-environment-variables-static-vs-dynamic-smackdown/

amedee.be - 🧪 GitHub Actions and Environment Variables: Static vs. Dynamic Smackdown

Let’s talk about environment variables in GitHub Actions — those little gremlins that either make your CI/CD run silky smooth or throw a wrench in your perfectly crafted YAML. If you’ve ever …

amedee.be

Great! There is finally a GitHub Actions policy to supports blocking and SHA pinning actions - GitHub Changelog https://github.blog/changelog/2025-08-15-github-actions-policy-now-supports-blocking-and-sha-pinning-actions

#GitHub #GitHubActions

GitHub Actions policy now supports blocking and SHA pinning actions - GitHub Changelog

GitHub Actions is powered by a diverse ecosystem of first-party and community contributed actions. If one of these actions has a vulnerability or is compromised by a malicious actor, it…

The GitHub Blog

GitHub Actions: Docker Compose замість сервісів

Помітив ненароком, що у збірці цілих 2 з половиною хвилини займає запуск сервісів. Це, якщо не стикався, всілякі бази даних та інші залежності, які є просто контейнерами Docker, чого ніхто й не приховує.

Втім, при уважному роздивлянні виявилось, що сервіси запускаються чомусь послідовно. Хоча я звик, що Docker Compose запускає їх паралельно. Про це навіть є запит, який, чомусь мені здається, навряд чи буде виконаний, але то інша тема.

Вихід, відповідно, очевидний — замінити сервіси на Docker Compose. Кумедно, що весь блок конфігурації services буквально копіюється у docker-compose.yml практично без змін. Потім на початку збірки (другим кроком після checkout) запускаємо docker compose up --detach та бачимо запуск вже за 45 секунд. Ось так, майже без зусиль, півтори хвилини заощаджено з кожної збірки.

Різниці у використанні немає — сервіси так само будуть доступні за тими ж портами, які були налаштовані раніше. Хіба що єдиний недолік — журнал контейнерів з сервісами ми просто так не побачимо. Хоча якщо він прямо потрібний, можна ж забрати з Docker без проблем.

Окреме питання — це величезні образи залежностей, які доводиться тягнути, а саме - OpenSearch, який важить майже гігабайт. Та й запускається він повільніше за всіх. Такий він, Web Scale!

PS. Самому хочеться щось вже позбавитись тих Actions разом із GitHub, але ж для роботи він точно ще довго залишиться.

#GitHubActions

Workflow syntax for GitHub Actions - GitHub Docs

A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your workflow configuration.

GitHub Docs

Time to make a move? #GiveUpGitHub

My new blog post is just out #BurgeonLab

➡️ https://www.burgeonlab.com/blog/migrate-github-pages-to-sourcehut-bunny/

It's a thorough guide of switching from an automated CI static site deployment workflow using GitHub Pages & GitHub Actions 🔄 to SourceHut Git and Builds + hosting on Bunny.net Storage & Bunny CDN.

#techguides #blog #blogging #blogpost #hugo #cicd #CDN #bunnycdn #bunnynet #github #sourcehut #githubactions #githubpages #srht

GitHub Pages Alternative: SourceHut Builds + Bunny.net

Learn how to replace GitHub Pages with SourceHut Builds, Bunny Storage, and Bunny CDN. Set up a CI static site workflow with a complete GitHub migration guide.

Burgeon Lab
thomasmerz - Overview

Linux since 1994. Motördad since 2005. Metal since cradle. Supporting Digitalcourage, EFF, FSF, GI, Mozilla, Pi-Hole, Red Cross, Syncthing, Wikimedia, … - thomasmerz

GitHub
GitHub - actions/checkout: Action for checking out a repo

Action for checking out a repo. Contribute to actions/checkout development by creating an account on GitHub.

GitHub

name: Weekly Download of Uptime Check Files

on:
schedule:
- cron: '0 0 * * SUN' # Every Sunday at midnight UTC
workflow_dispatch: # Allows manual trigger from GitHub UI

jobs:
download_json_files:
runs-on: ubuntu-latest

steps:
- name: Checkout repository with full history
uses: actions/checkout@v2
with:
fetch-depth: 0

- name: Download JSON files to root directory
run: |
curl -o ./alcea-wisteria.de.json https://alcea-wisteria.de/PHP//0demo/2025-08-04-UptimeCheck/alcea-wisteria.de.json
curl -o ./alceawis.com.json https://alcea-wisteria.de/PHP//0demo/2025-08-04-UptimeCheck/alceawis.com.json
curl -o ./alceawis.de.json https://alcea-wisteria.de/PHP//0demo/2025-08-04-UptimeCheck/alceawis.de.json

- name: Commit and push changes
run: |
set -e
git config --global user.name 'github-actions'
git config --global user.email 'github-actions@github.com'
git add ./*.json
if git diff --cached --quiet; then
echo "No changes to commit"
else
git commit -m "Weekly download of uptime check JSON files"
if ! git pull --rebase origin main; then
echo "❌ Rebase failed due to conflicts. Keeping remote changes and skipping push."
git rebase --abort || true
exit 0
fi
git push origin main
fi

X https://github.com/Ry3yr/ry3yr.github.io/actions/runs/16855638849/workflow
https://github.com/Ry3yr/ry3yr.github.io/actions/runs/16865761973

Had to rewrite the stupid yml to even get it to work..
No wonder I no longer use #github much ( <3 Litespeed )

This is a burden
https://chatgpt.com/share/6898f7fa-f734-800e-ace5-59613ef70169
 
In the end I had to ask AI chan cause this is very confusing.

I hate #git ..
Maybe I need2 



#repost •acws #acws #github #GithubActions #Commit
🌘 如何使用 netcat 與 GitHub Actions 進行互動式除錯
➤ 讓 GitHub Actions 在失敗時,也能任你 SSH 探索!
https://jacobtomlinson.dev/posts/2021/how-to-interactively-debug-github-actions-with-netcat/
本文介紹一種實驗性的除錯方法,教你如何透過建立一個反向 Shell (reverse shell),使 GitHub Actions 工作流程在執行失敗時,能讓你從本地端連線至 CI 執行器,進行即時互動式除錯。作者詳細說明瞭如何利用 `netcat` 接收連線、`ngrok` 進行 port forwarding,以及如何在 GitHub Actions 工作流程中設定指令來建立此反向 Shell。文末也補充了作者後續發現更簡便的 `tmate` Action 作為替代方案。
+ 這個方法很有趣,雖然有安全疑慮,但對於需要快速診斷 CI 失敗原因的場景,絕對是一
##GitHubActions #除錯 #netcat #ReverseShell
How to interactively debug GitHub Actions with netcat

Update: This was a fun experiment and I recommend you check out the post for a fun read on setting up reverse shells. But I’ve since discovered this awesome tmate action which lets you interactively debug in the browser or via SSH.

×

GitHub Actions now provide ARM64 runners!

Starting from today, all GitHub Actions users can now use the ARM64 runners that use the Ubuntu Linux 22.04 and 24.04 operating systems, as well as Windows 11 ARM64. This now matches what we already have in GitLab for Linux runners. According to the official GitHub blog article, the ARM64 runner for both Linux and Windows is now generally available, long after the macOS ARM64 runners were available for months.

The following runners can be used in standard GitHub workflow files:

  • windows-11-arm: Uses the Windows 11 ARM64 image provided by Arm LLC.
  • ubuntu-24.04-arm: Uses the Ubuntu 24.04 Noble Numbat ARM64 image.
  • ubuntu-22.04-arm: Uses the Ubuntu 22.04 Jammy Jellyfish ARM64 image.

Those runners are for public repositories and are not meant to be run in private repositories in either your account or your organization. In order to be able to use those images, you should use the larger runners. This is one step ahead of GitLab by providing the Windows 11 ARM64 runner for free.

You can see the full list of runners that you can use here.

On the side note, we are still experiencing problems with the GitHub runners in our organization, and this makes us unable to use any of those runners.

#arm64 #github #GitHubActions #news #Tech #Technology #update