Remote Ruby Unraveling GitHub Actions & Modern Auth Challenges
Mar 20, 2026
They dig into a multi-hour GitHub Actions CI debugging saga and explain artifact upload/download quirks and workflow run triggers. They debate agentic AI workflows, low-quality AI PRs, and rising infrastructure costs. Legacy authentication headaches and the mental toll of maintaining Vue 2 alongside Vue 3 come up. Neovim setups and ERB tooling improvements are also discussed.
AI Snips
Chapters
Transcript
Episode notes
Auth Work Tore Through Fragmented Legacy Code
- Andrew spent weeks untangling auth spread across multiple places in a legacy app and found meetings took longer than coding.
- He discovered a partial earlier attempt left fragmented logic in 3–4 locations, forcing rework and meetings to decide intended behavior.
CI Nightmares Caused By Identical Artifact Names
- Chris spent hours debugging a GitHub Actions pipeline where two builds produced identical executable names and the release upload failed with 404s.
- The culprit was identical file names inside different extracted artifact folders and an upload clobber flag that removed other assets unpredictably.
Skip Zipping Single Artifacts And Adjust Retention
- Use upload-artifact v7's archive=false to avoid zipping single files and set retention to keep storage under control.
- Chris learned artifacts default to zips and retention defaults to 90 days, so adjust retention or archive settings for temporary build files.