Putting an End to “Isn’t this the Same Root Cause as That Project Six Months Ago? Why Didn’t You Prevent It?” — Reusable Workflows …
summary
A 15-repo Android team built a single Markdown "common Android issue" catalog and used GitHub Actions Reusable Workflows plus Copilot to distribute it, but found engineers didn’t add entries. They switched to an automated pipeline: Claude runs in GitHub Actions to analyze PR diffs, detect cross-project common issues, generate structured catalog entries and auto-PR them; after review those entries are propagated via Reusable Workflows and referenced by Copilot code reviews, keeping shared safeguards up to date across projects.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:05Structural causes of failures
- 5:36Guardrails for recurrence
- 7:57How reusable workflows work
- 11:24Implementation notes
- 16:08Copilot instructions
- 20:31Knowledge sharing failures
- 24:05AI-driven failure files
- 30:19Bloating in files
- 33:36Outcomes and summary
related talks
40mAutomating Android Workflows with Github Actions
01h 47mDeveloper Workflow Automation with GitHub Actions
20mSetting up and managing GitHub actions for multiple projects
45mA Call to (GitHub) Actions!
45mLights, Camera, GitHub Actions!
25mAutomate Maintainer Tasks With GitHub Actions
48mBuilding an Android CI Pipeline With GitHub Actions
30mForget Mono vs. Multi-Repo: Building Centralized Git Workflows for All Apps