Skip to content

fix(workflows): trigger deploy on content/** changes#29

Merged
superterran merged 1 commit intomainfrom
fix/deploy-on-content-changes
May 9, 2026
Merged

fix(workflows): trigger deploy on content/** changes#29
superterran merged 1 commit intomainfrom
fix/deploy-on-content-changes

Conversation

@superterran
Copy link
Copy Markdown
Contributor

Summary

  • The Deploy to Micro.blog workflow only triggered on layouts/, static/, theme.toml, plugin.json changes. Blog post merges under content/blog/** did not kick off a rebuild.
  • 10 markdown posts have accumulated in content/blog/ since the last theme-touching deploy on 2026-04-25, but https://doughatcher.com/blog/ still only shows the SOW post.
  • Adds content/** to the path filter so future blog merges trigger a Micro.blog rebuild.

After Merge

Merging this PR alone will not deploy — .github/workflows/deploy.yml itself isn't in the trigger paths. Run once manually to publish the backlog:

gh workflow run deploy.yml

Subsequent blog merges will then trigger automatically.

Test plan

  • Merge to main
  • Manually dispatch the workflow once to publish the backlog
  • Confirm all 10 posts appear at https://doughatcher.com/blog/
  • Verify the next blog post merge triggers a deploy on its own

🤖 Generated with Claude Code

Blog post merges weren't triggering Micro.blog rebuilds because the
deploy workflow's path filter excluded content/. New posts since the
last theme-touching deploy on 2026-04-25 sat in the repo without
appearing on the live site.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@superterran superterran merged commit 5004f87 into main May 9, 2026
1 check passed
@superterran superterran deleted the fix/deploy-on-content-changes branch May 9, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant