Menu

1 / 2

Why I reused a single CI pipeline for two YouTube channels and three SEO sites

DEV Community·盛永裕介·6 months ago
#ddHiA8CF
#githubactions#showdev#youtube#queue#channels
Reading 0:00
15s threshold

This morning I scaffolded @royal_lore , a second YouTube channel that runs on the exact same scripts/yt-publish/ pipeline that already powers my first channel. The content bank I wrote covers 32 historical queens — Egyptian, European, Chinese, Indian, Russian, Aztec, African — across five narrative angles each: "who she was," "why she's underrated," "what historians argue about," "what she built," "how she died." That's 160 videos at one per day — roughly five months of content before I need to refill the bank.

Zero new CI code.

What I actually built

The scaffolding for the new channel was four files:

.github/workflows/yt-publish-royal.yml — a dedicated workflow pointing at content/yt-queue-royal/ as its queue directory and ROYAL_YT_* secrets for OAuth

content/yt-queue-royal/ — an empty queue directory with a .gitkeep

content/yt-queue-royal/uploaded/ — where the workflow archives processed items after upload

docs/royal-queens-bank-en.md — 179 lines of structured content prompts

The entire upload path…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.