[CI] Migrate to npm-managed local Hugo and standardise Makefile targets#408
[CI] Migrate to npm-managed local Hugo and standardise Makefile targets#408hebypaul wants to merge 3 commits into
Conversation
Signed-off-by: Heby T Paul <hebytpaul1111@gmail.com>
There was a problem hiding this comment.
Code Review
This pull request migrates the project's build and development workflow to use a locally managed Hugo binary via npm, updating the Makefile, README, and package.json scripts accordingly. Feedback on these changes highlights that the theme-update target in the Makefile still incorrectly references the global hugo binary instead of the local one. Additionally, the clean target in the Makefile and the dev:clean script in package.json are redundant and inefficient, and should be refactored or removed to properly clean build artifacts.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
🚀 Preview deployment: https://layer5io.github.io/exoscale-academy/pr-preview/pr-408/
|
Signed-off-by: Heby T Paul <hebytpaul1111@gmail.com>
… update scripts Signed-off-by: Heby T Paul <hebytpaul1111@gmail.com>
Notes for Reviewers
This PR migrates the
exoscale-academybuild process to use an npm-managed local Hugo dependency, standardizing the local development experience and mitigating version mismatch issues.Specific updates include:
check-depstarget to theMakefileto validatenpmand the localhugobinary.site,serve,build, andcleancommands to triggernpm runscripts.dev:*scripts topackage.jsonto handle Hugo commands with the correct flags, stripping out unnecessarynpxprefixes.README.mdto remove references to a globally installed Hugo and emphasize the newmake setup->make siteworkflow.This PR fixes #407
Signed commits