Repo hygiene: disable make-publish footgun, silence permanent build error - #57
Merged
Merged
Conversation
… error - make publish built with the DEV config (relative URLs, wrong canonicals, no feeds) and force-pushed gh-pages, bypassing every CI guard. Now fails with a pointer at the PR flow; deploys are Actions-only (deploy.yml). - exclude content/tools/ from article/page scanning so the markdown reader stops logging an ERROR on the vendored VENDORED.md every build; the tool page itself is static-shipped and unaffected.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two small fixes, no site-output changes beyond removing log noise.
make publish is now an error
The old target built with the DEV config (
pelicanconf.py:RELATIVE_URLS=True, wrong canonicals, no feeds) and force-pushedgh-pagesdirectly - bypassing all CI guards. One habitual run would deploy a broken site over the guarded one. The target now exits 1 with a pointer at the PR flow; deploys remain GitHub-Actions-only.VENDORED.md build error silenced
Every build logged
ERROR Skipping .../tools/iam-blast-radius/VENDORED.md: could not find information about 'title'.content/tools/is static-shipped, so it's now inARTICLE_EXCLUDES/PAGE_EXCLUDES. A guaranteed-red line in every build is how real ERRORs get ignored.Verified locally
output/tools/iam-blast-radius/index.htmlstill shipsmake publishexits non-zero with guidance