blog: add copy-paste Lovable AI prompt for Capgo Actions

[riderx]

Summary

• Replace Step 3 Option A/B with one copy-paste Lovable AI instruction (exact workflow YAML + rules)
• Follow-up to blog: Lovable → Capgo live updates via GitHub Actions #928 (prompt commit landed after that PR merged)

Test plan

• Preview /blog/automate-capgo-live-updates-from-lovable-github-actions/
• Confirm the Lovable prompt block is easy to copy as one block

Made with Cursor

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• Documentation
  • Updated the Lovable and GitHub Actions setup guide with a complete workflow prompt.
  • Clarified secret handling, build-script and lockfile fallbacks, prohibited configuration changes, and commit behavior.
  • Added Lovable Publish follow-up steps.
  • Refined guidance for manual setup and configuring the Vite base path when remediation is needed.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_7cf8fdd0-f02d-4ab5-b9fd-2af535a95bcd)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: ecec6d0b-fc22-4bbc-9458-3b8b9c7960c9

📥 Commits

Reviewing files that changed from the base of the PR and between eca9b7b and e1bf3fd.

📒 Files selected for processing (1)

• apps/web/src/content/blog/en/automate-capgo-live-updates-from-lovable-github-actions.md

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• Cap-go/capacitor-updater (manual)

---

📝 Walkthrough

Walkthrough

The blog guide now uses one complete Lovable instruction for GitHub Actions setup. It defines workflow requirements, fallback behavior, configuration limits, commit and publish steps, a manual alternative, and Vite base remediation.

Changes

Lovable workflow guide

Layer / File(s)	Summary
Workflow setup instructions apps/web/src/content/blog/en/automate-capgo-live-updates-from-lovable-github-actions.md	The guide replaces the previous setup choices with a direct Lovable prompt. The prompt defines token handling, build and lockfile fallbacks, configuration limits, commit behavior, and publishing. It also updates the manual workflow and Vite guidance.

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

Possibly related PRs

• Cap-go/website#928: Updates the same Lovable-to-Capgo GitHub Actions blog post and workflow instructions.

Suggested reviewers: actions-user

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a copy-paste Lovable AI prompt to the Capgo Actions blog post.
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.

---

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

[coderabbitai]

Actionable comments posted: 3

🤖 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
`@apps/web/src/content/blog/en/automate-capgo-live-updates-from-lovable-github-actions.md`:
- Around line 120-126: Run the required visual diff for the Markdown blog
content by capturing renders of the base-branch and changed versions, comparing
them, and adding the resulting report to the pull request description.
- Around line 74-80: Reconcile the workflow guidance around
capgo-live-updates.yml: instruct Lovable to start from the provided YAML, then
adapt the build command and dependency installation to the project’s available
scripts and lockfile while preserving the required workflow behavior. Update the
manual alternative to use that same adapted workflow rather than requiring the
unmodified YAML.
- Around line 114-115: Replace every newly introduced npm and npx workflow
instruction in the article with equivalent Bun commands, including dependency
installation, production builds, CLI execution, caching, lockfile fallback, and
troubleshooting guidance. Use the repository’s bun.lock and Bun build scripts
consistently, while preserving the existing guidance to prefer the project’s
actual production build script.

🪄 Autofix

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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c0a286a6-13bb-44bf-b1cb-57e7ba2bdf16

📥 Commits

Reviewing files that changed from the base of the PR and between 139bd8c and eca9b7b.

📒 Files selected for processing (1)

• apps/web/src/content/blog/en/automate-capgo-live-updates-from-lovable-github-actions.md

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• Cap-go/capacitor-updater (manual)

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_e8a4f56d-068a-4249-873e-f4cb03e151ef)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud