Consolidating Sentry Cron Check‑ins & Adding Dynamic Inputs to GitHub Actions Workflows in **content‑automation**
Consolidating Sentry Cron Check‑ins & Adding Dynamic Inputs to GitHub Actions Workflows in content‑automation TL;DR: I refactored the four separate Sentry cron check‑ins into a single monitor and exposed --lang/--repo as workflow_dispatch inputs for the Bluesky workflow. The changes cut CI noise, made the pipelines configurable at run‑time, and forced me to rewrite a broken Groq‑AI integration that was crashing the content generator. Our content‑automation repo runs four daily GitHub Actions workflows: devto-daily.yml bluesky-daily.yml daily-content.yml weekly-newsletter.yml Each workflow perf
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in