Urgent.News

What's breaking now, across thousands of outlets.

Sunday, 15 November 2026 Reading Room

Tech

GitHub Actions vs Argo Workflows: which one runs what

GitHub Actions vs Argo Workflows is usually a false choice, because the two are not sold the same unit of work: Actions runs a workflow file in response to a git event, and Argo Workflows reconciles a Kubernetes custom resource that models a DAG of containers. The place they genuinely collide is fan-out, where Actions caps a job matrix at 256 jobs per run and Argo is bounded by the cluster. The…

dev.to ·

The article compares GitHub Actions and Argo Workflows, two different tools for managing workflows, and explains that they are not designed for the same purpose. GitHub Actions is triggered by events in a Git repository, such as pushes or pull requests, and runs a workflow file in response to these events. It shares a single runner and filesystem, and caps a job matrix at 256 jobs per run.

Argo Workflows, on the other hand, is implemented as a Kubernetes Custom Resource Definition (CRD) and reconciles a DAG (Directed Acyclic Graph) of containers. It does not have its own git trigger; instead, event-driven triggering is done through a separate project called Argo Events.

The main similarity between the two is that they both support fan-out, but they differ in their implementation. GitHub Actions limits a job matrix to 256 jobs per run, while Argo Workflows is bounded by the Kubernetes cluster. Each step in Argo Workflows runs in its own Pod, historically with three containers: main, init, and wait.

This design is suitable for running machine learning pipelines, data and batch processing, infrastructure automation, and CI/CD pipelines, but not ideal for CI jobs with multiple steps that could share a disk.

The fan-out ceiling is the real reason to compare the two tools, as GitHub Actions has a hard limit of 256 jobs per workflow run, while Argo Workflows has no published limit, and its bottleneck is the cluster it runs on. The article concludes that the choice between the two should be based on the shape of the workflow rather than which is better.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Paid in USDC, Living in Indonesia: How I Use Raenest to Receive, Hold and Spend Stablecoins

I work in web3 from Indonesia, and a growing share of my work — bounties, contests, research and security gigs — pays in USDC on Solana. Getting paid was never the hard part.

  • Author receives payments in USDC and USDT stablecoins while living in Indonesia.
  • Raenest platform enables users to receive, hold, convert, spend, and transfer stablecoins.
  • Virtual or physical Visa cards allow spending stablecoins anywhere Visa is accepted.

·dev.to

ZQN-12B: our second open model, plus the M3-GPTQ compression paper

ZQN-12B is the second open model from ZAQERIS Ai, an independent AI research group in Cairo, Egypt. Trained from scratch 15.55B parameters, compressed with our ZAQERIS M3-GPTQ method to 6.48 GiB (3.25…

  • ZQAERIS Ai releases ZQN-12B, their second open model with 15.55B parameters.
  • Model compressed to 6.48 GiB using ZAQERIS M3-GPTQ compression method.
  • ZQN-12B offers 128K context window, expandable to 256K with YaRN technique.

·dev.to

Don't Trust the Agent. Verify the Gatekeeper — Then Verify Everything Else Too.

#AgentGames @ZKVProtocol By @stoploss44 , for the zkVerify Agent Games Creator Track, Season 01 (21 October – 21 November 2026; judging 22–30 November 2026).

  • Agent Games competition aims to create Proof Gatekeeper AI
  • AI agent must verify payment request validity before issuing proof
  • Proof Gatekeeper must pass circuit test, but correctness not guaranteed

·dev.to

More from Sunday 15 November →