Skip to content

fix: update site-build workflow for website/ → docs/ move - #51

Open
maruiz93 wants to merge 1 commit into
fullsend-ai:mainfrom
maruiz93:fix-site-build-workflow
Open

fix: update site-build workflow for website/ → docs/ move#51
maruiz93 wants to merge 1 commit into
fullsend-ai:mainfrom
maruiz93:fix-site-build-workflow

Conversation

@maruiz93

Copy link
Copy Markdown
Contributor

Summary

  • Update paths in the "Build Doc Site" workflow to reflect fullsend's website/docs/ reorganization (commit 8f3a4363)
  • Bump actions/checkout to v7.0.1 and actions/setup-node to v6.5.0 to match fullsend repo
  • Add comments explaining the cross-repo symlink and why npx vitepress build docs is used instead of npm run docs:build

Test plan

  • "Build Doc Site" check passes on this PR (setup-node cache resolves, npm ci succeeds, vitepress build completes)

Closes #50

🤖 Generated with Claude Code

fullsend commit 8f3a4363 moved VitePress from website/ to docs/ and
package-lock.json to the repo root, breaking the cross-repo doc site
build in experiments.

Also bumps actions/checkout to v7.0.1 and actions/setup-node to v6.5.0
to match the fullsend repo.

Closes fullsend-ai#50

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Marta Anon <manon@redhat.com>
@maruiz93
maruiz93 requested a review from a team as a code owner August 11, 2026 12:12
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Fix doc-site build workflow after fullsend website/ → docs/ reorg

🐞 Bug fix ⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

AI Description

• Update Build Doc Site workflow paths for fullsend’s website/ → docs/ move.
• Align pinned GitHub Actions versions with upstream fullsend workflow.
• Preserve experiments content injection via symlink and build with VitePress directly.
Diagram

graph TD
  W["site-build.yml"] --> E[("experiments checkout")] --> F[("fullsend checkout")] --> N["setup-node + npm cache"] --> I["npm ci"] --> S["symlink docs/experiments"] --> B["vitepress build docs"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Run `npm run docs:build` and configure submodule auth
  • ➕ Keeps build invocation aligned with fullsend’s intended scripts
  • ➕ Avoids relying on VitePress CLI behavior staying stable
  • ➖ Requires SSH keys or token-based auth for submodule update in CI
  • ➖ Higher maintenance and greater risk of intermittent CI failures
2. Copy experiments content into docs/ instead of symlinking
  • ➕ Avoids symlink edge-cases on some runners/tools
  • ➕ More explicit, less dependent on filesystem link semantics
  • ➖ Extra build step and potentially slower CI
  • ➖ Risk of stale content if copy step misses paths or exclusions

Recommendation: Keep the current approach: adjust paths for the docs/ move, replace the experiments submodule with a symlink, and run npx vitepress build docs directly. It minimizes CI secrets/auth complexity while preserving the cross-repo “combined site” build behavior.

Files changed (1) +12 / -9

Other (1) +12 / -9
site-build.ymlFix doc-site build workflow paths and VitePress build invocation +12/-9

Fix doc-site build workflow paths and VitePress build invocation

• Updates the workflow to install/build from the fullsend repo root after the VitePress site moved from website/ to docs/. Adjusts npm cache dependency path to the root package-lock.json, refreshes pinned checkout/setup-node action SHAs, and replaces the previous submodule/symlink steps with a single docs/experiments symlink plus a direct 'vitepress build docs' call to avoid submodule updates.

.github/workflows/site-build.yml

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 11, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 12:13 PM UTC · Completed 12:24 PM UTC

Commit: ffb7906 · View workflow run →

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@fullsend-ai-review

Copy link
Copy Markdown

Review

Findings

Medium

  • [protected-path] .github/workflows/site-build.yml — This PR modifies a file under the protected .github/ path. The linked issue (Build Doc Site workflow broken since fullsend moved website/ to docs/ #50) provides clear context for why the workflow file needs updating (fullsend's website/docs/ reorganization broke the build), and the changes are well-scoped to the reported problem. Human approval is always required for protected-path changes, regardless of context.

Low


Labels: PR fixes a broken CI workflow (.github/workflows/) under protected paths

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

steps:
- name: Checkout experiments
uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[low] scope-creep

Dependency version bumps (actions/checkout v7.0.0 to v7.0.1, actions/setup-node v6.4.0 to v6.5.0) are not explicitly authorized by issue #50. The issue authorizes fixing the broken workflow by updating paths, not bumping action versions. The PR body acknowledges these bumps are to match fullsend repo which is a separate maintenance concern.

Suggested fix: Remove the dependency version bumps from this PR and submit them separately, or update issue #50 to explicitly authorize bumping dependencies.

@fullsend-ai-review fullsend-ai-review Bot added requires-manual-review Review requires human judgment bug Something isn't working labels Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working requires-manual-review Review requires human judgment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build Doc Site workflow broken since fullsend moved website/ to docs/

1 participant