next carries one change beyond main: script/lint now fails on any Hugo warning, including Hugo's warning that two pages write the same output path. The lint build in Dockerfile.lint adds Hugo's own --panicOnWarning; comments, the README and TODO.md say so.
To know before merging: from now on a Hugo upgrade that adds a new warning, or a page the theme has no layout for, fails make check, the pre-commit hook and CI until it is fixed. The deploy workflow runs only script/test, so a warning never blocks a deploy. The published site is unchanged.
Model: opus-5-5
`next` carries one change beyond `main`: `script/lint` now fails on any Hugo warning, including Hugo's warning that two pages write the same output path. The lint build in `Dockerfile.lint` adds Hugo's own `--panicOnWarning`; comments, the README and `TODO.md` say so.
To know before merging: from now on a Hugo upgrade that adds a new warning, or a page the theme has no layout for, fails `make check`, the pre-commit hook and CI until it is fixed. The deploy workflow runs only `script/test`, so a warning never blocks a deploy. The published site is unchanged.
Model: opus-5-5
The lint step in Dockerfile.lint now passes --panicOnWarning alongside
--printPathWarnings. Until now Hugo printed "Duplicate target paths"
when two pages wrote the same output file and still exited 0, so the
lint passed while one page was silently lost. The flag turns that
warning, and every other Hugo warning, into a failed lint.
script/test and the deploy build are unchanged. The comments in
Dockerfile.lint, script/lint and script/check, the README entry for
script/lint, and TODO.md now describe the stricter lint.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
nextcarries one change beyondmain:script/lintnow fails on any Hugo warning, including Hugo's warning that two pages write the same output path. The lint build inDockerfile.lintadds Hugo's own--panicOnWarning; comments, the README andTODO.mdsay so.To know before merging: from now on a Hugo upgrade that adds a new warning, or a page the theme has no layout for, fails
make check, the pre-commit hook and CI until it is fixed. The deploy workflow runs onlyscript/test, so a warning never blocks a deploy. The published site is unchanged.Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.