Skip to content

chore: restructure into the THectic Hugo-site pattern - #106

Merged
Stensel8 merged 2 commits into
mainfrom
hugo-site
Sep 3, 2026
Merged

chore: restructure into the THectic Hugo-site pattern#106
Stensel8 merged 2 commits into
mainfrom
hugo-site

Conversation

@Stensel8

@Stensel8 Stensel8 commented Sep 3, 2026

Copy link
Copy Markdown
Member

Adds a Hugo (Hextra theme) landing page under src/ for scripts.thectic.nl, deployed to Bunny.net — mirroring the pattern already applied to BypassNRO, Zephyrus-Linux, and staged (also draft) for WinDeploy.

validate-scripts.yml and update-nginx-checksums.yml are untouched — this only adds the site plus the org's standard hygiene CI (config-validation, pr-title, trivy-scan, deploy-bunny) alongside them.

All Stensel8/Scripts references updated to Thectic-NL/Scripts in README.md and .github/TESTING_AUTOMATION.md.

What I could verify from here

  • All new/changed workflow YAML parses clean (including the two pre-existing ones)
  • go mod download for github.com/imfing/hextra v0.12.3 succeeds directly against proxy.golang.org

What I could not verify from here

  • A full hugo --gc --minify build. This sandbox's egress proxy blocks go.dev's toolchain-download endpoint (go.mod requires go 1.26, newer than this sandbox's base Go) — the same limitation flagged in the WinDeploy PR. go.mod/go.sum/hugo.toml are structurally identical to BypassNRO's already-working production files (only name/URL/content differ).

What I could not do from here — needs you

  • The actual repo transfer to Thectic-NL. No GitHub API transfer tool is available to me, and it's the kind of hard-to-reverse, cross-account action that belongs behind a manual click in GitHub Settings → Danger Zone, not something to attempt blind.
  • Bunny.net secrets: BUNNY_STORAGE_ZONE, BUNNY_ACCESS_KEY, BUNNY_STORAGE_ENDPOINT, BUNNY_API_KEY, BUNNY_PULL_ZONE_ID.
  • A Bunny Pull Zone + DNS entry for scripts.thectic.nl.
  • A project card on Thectic-NL/THectic.nl's homepage (data/projects/overrides.yaml) and/or the thectic-project topic on the repo once transferred, so it shows on the org homepage grid.

Marked draft since it can't actually deploy or go live until the transfer happens — flip to ready whenever.

Adds a Hugo (Hextra theme) landing page under src/ for
scripts.thectic.nl, deployed to Bunny.net, mirroring the pattern
applied to BypassNRO, Zephyrus-Linux, and (pending) WinDeploy. The
existing validate-scripts.yml and update-nginx-checksums.yml stay as
they are; this only adds the site plus the org's standard hygiene CI
(config-validation, pr-title, trivy-scan, deploy-bunny) alongside
them.

Stensel8/Scripts references in README.md and TESTING_AUTOMATION.md
updated to Thectic-NL/Scripts.

Verification from this sandbox: all new workflow YAML parses clean;
`go mod download` for the hextra module succeeds directly against
proxy.golang.org. A full `hugo --gc --minify` build could not be
confirmed here — this sandbox's egress proxy blocks go.dev's
toolchain-download endpoint (go.mod requires go 1.26, newer than this
sandbox's base Go), the same limitation noted in the WinDeploy PR.
go.mod/go.sum/hugo.toml are structurally identical to BypassNRO's
already-working production files.

Needs, before this can go live:
- The actual transfer of this repo to Thectic-NL — no API tool for
  that is available here, and it's a hard-to-reverse, cross-account
  action better done by hand in GitHub Settings.
- BUNNY_STORAGE_ZONE, BUNNY_ACCESS_KEY, BUNNY_STORAGE_ENDPOINT,
  BUNNY_API_KEY, BUNNY_PULL_ZONE_ID as repo secrets, plus a Bunny Pull
  Zone/DNS entry for scripts.thectic.nl.
- A project card on Thectic-NL/THectic.nl's homepage (data/projects/
  overrides.yaml), and/or the thectic-project topic on the repo once
  transferred.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T7WUzzVA6cZooJ7CVVUeQo
…y choice

config-validation.yml's actionlint step scans every workflow file,
including the pre-existing validate-scripts.yml — and failed on 14
info/style-level shellcheck findings there (mostly SC2086 on unquoted
$GITHUB_STEP_SUMMARY, plus SC2129 style suggestions).

That file already runs `shellcheck -S warning` itself in its "Run
ShellCheck" step, a deliberate choice to treat info/style findings as
non-blocking. actionlint's embedded shellcheck integration doesn't
read a repo .shellcheckrc (tested locally — no effect), so left as-is
it silently re-imposes error-level severity on the same scripts.
Matches the existing convention via actionlint's own ignore mechanism
instead of editing someone else's already-working workflow.

Verified locally: actionlint (pinned v1.7.12, sha256 checked) now
exits 0 across all workflow files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T7WUzzVA6cZooJ7CVVUeQo
@Stensel8
Stensel8 marked this pull request as ready for review September 3, 2026 07:54
Copilot AI lite review requested due to automatic review settings September 3, 2026 07:54

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@Stensel8
Stensel8 merged commit bc9f342 into main Sep 3, 2026
4 of 5 checks passed
@Stensel8
Stensel8 deleted the hugo-site branch September 3, 2026 07:54
@Stensel8 Stensel8 self-assigned this Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants