Trigger Website Rebuild On Merge

[jbolda]

Motivation

Instead of manual button pressing. Trigger website rebuild on merge.

Summary by CodeRabbit

• Chores
  • Added an automated GitHub Actions workflow to trigger website rebuilds via both manual runs and updates to the main branch.
  • Enabled coordinated, single-at-a-time execution with a defined timeout for reliable rebuild scheduling.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: bac9dfe8-6ccd-49a4-a3ac-69b313f686b4

📥 Commits

Reviewing files that changed from the base of the PR and between 2d4a26f and bf15db1.

📒 Files selected for processing (1)

• .github/workflows/www.yaml

---

📝 Walkthrough

Walkthrough

Adds a GitHub Actions workflow triggered manually or by pushes to main. It runs on Ubuntu and dispatches www.yaml in the thefrontside/effection repository using the configured GitHub token.

Changes

Workflow Dispatch Integration

Layer / File(s)	Summary
Downstream workflow trigger .github/workflows/www.yaml	Configures manual and main push triggers, a five-minute Ubuntu job, and a token-authenticated command to dispatch the downstream workflow.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes Motivation but omits the required Approach section from the template.	Add an Approach section that briefly summarizes the workflow change, including the push/dispatch trigger and rebuild action.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the main change: triggering a website rebuild on merge.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Policy Compliance	✅ Passed	Only a .github/workflows change; version-bump policy exempts CI/workflow files, and the PR description has no AI marketing or co-author footer.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch trigger-www

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/www.yaml:
- Around line 3-7: Add a workflow-level concurrency configuration to the www
workflow triggered by pushes to main, using a stable group key and
cancel-in-progress enabled so newer runs cancel superseded ones. Place the
concurrency block alongside the existing on configuration.
- Around line 9-12: Add a job- or workflow-level permissions block for the
trigger-effection-rebuild job, setting the GITHUB_TOKEN permissions to none.
Preserve the existing PAT-based gh workflow run behavior and do not grant
unnecessary scopes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: a64e8036-a8e1-44e0-834e-0fcbfc29c5a1

📥 Commits

Reviewing files that changed from the base of the PR and between 387f725 and 2d4a26f.

📒 Files selected for processing (1)

• .github/workflows/www.yaml