<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github-Actions on Codes</title><link>https://codes.metacog.co.kr/tags/github-actions/</link><description>Recent content in Github-Actions on Codes</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© {year} jeonck. Distributed under [MIT](https://opensource.org/licenses/MIT).</copyright><lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://codes.metacog.co.kr/tags/github-actions/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Cloud Routine vs. GitHub Actions cron: they look the same but you manage them differently</title><link>https://codes.metacog.co.kr/posts/claude-cloud-routine-vs-github-actions-cron/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://codes.metacog.co.kr/posts/claude-cloud-routine-vs-github-actions-cron/</guid><description>A repo with no visible cron workflow isn&amp;rsquo;t proof there&amp;rsquo;s no automated publishing. The schedule and generation logic can live entirely outside the repo, on Claude&amp;rsquo;s side.</description></item><item><title>Commit message language is a per-repo decision — and the automation template needs updating too</title><link>https://codes.metacog.co.kr/posts/commit-message-language-per-repo-convention/</link><pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate><guid>https://codes.metacog.co.kr/posts/commit-message-language-per-repo-convention/</guid><description>An English-facing site had commits piling up in Korean. Switching new commits to English seemed simple, until one easy-to-miss spot turned up.</description></item><item><title>Adding an LLM feature to a static site without ever putting a token in the browser</title><link>https://codes.metacog.co.kr/posts/static-site-llm-feature-github-issue-trigger/</link><pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate><guid>https://codes.metacog.co.kr/posts/static-site-llm-feature-github-issue-trigger/</guid><description>Two options came up first — an API key in localStorage, or a Cloudflare Worker proxy — and neither was it. A GitHub-issue trigger pattern was requested instead.</description></item></channel></rss>