Skip to content

chore: align CI/CD and layout with the other Thectic repos - #26

Merged
Stensel8 merged 1 commit into
mainfrom
chore/align-cicd-with-thectic
Sep 2, 2026
Merged

chore: align CI/CD and layout with the other Thectic repos#26
Stensel8 merged 1 commit into
mainfrom
chore/align-cicd-with-thectic

Conversation

@Stensel8

@Stensel8 Stensel8 commented Sep 2, 2026

Copy link
Copy Markdown
Member

Move the Hugo site into src/ and adopt the shared Thectic workflow set, matching Zephyrus-Linux (the closest analog: Hugo + hextra module).

CI fix: setup-go now uses go-version-file: src/go.mod, so the runner's Go matches what go.mod requires. Previously setup-go installed an older Go with GOTOOLCHAIN=local and hugo mod get -u failed with "go.mod requires go >= 1.26.0". go.mod pinned to go 1.26 to match the other repos.

Workflows:

  • deploy.yml -> deploy-bunny.yml, house style, builds from src/
  • config-validation.yml, pr-checks.yml, pr-title.yml, update-checksums.yml, trivy-scan.yml adopted from the shared set
  • powershell.yml kept (bypass.ps1 is core here), modernized: pinned SHAs, path filters, permissions: {}, concurrency
  • pr-checks runs markdownlint, EN/NL parity, Hugo build, internal link check

Bilingual: site is now EN + NL like Zephyrus. Added src/content/_index.nl.md, languages.nl, and the language-switch / theme-toggle menu entries.

Support files: .editorconfig, .gitattributes, .markdownlint.yml, .lychee.toml, CONTRIBUTING.md, pull_request_template.md, .github/scripts/, renovate.json (gomod manager + pinned-tool custom managers).

Drop stale bypassnro.stensel.nl / Stensel8/bypassnro references; everything is bypassnro.thectic.nl and Thectic-NL/BypassNRO now.

Move the Hugo site into src/ and adopt the shared Thectic workflow set,
matching Zephyrus-Linux (the closest analog: Hugo + hextra module).

CI fix: setup-go now uses go-version-file: src/go.mod, so the runner's Go
matches what go.mod requires. Previously setup-go installed an older Go with
GOTOOLCHAIN=local and `hugo mod get -u` failed with "go.mod requires go >=
1.26.0". go.mod pinned to `go 1.26` to match the other repos.

Workflows:
- deploy.yml -> deploy-bunny.yml, house style, builds from src/
- config-validation.yml, pr-checks.yml, pr-title.yml, update-checksums.yml,
  trivy-scan.yml adopted from the shared set
- powershell.yml kept (bypass.ps1 is core here), modernized: pinned SHAs,
  path filters, permissions: {}, concurrency
- pr-checks runs markdownlint, EN/NL parity, Hugo build, internal link check

Bilingual: site is now EN + NL like Zephyrus. Added src/content/_index.nl.md,
languages.nl, and the language-switch / theme-toggle menu entries.

Support files: .editorconfig, .gitattributes, .markdownlint.yml, .lychee.toml,
CONTRIBUTING.md, pull_request_template.md, .github/scripts/, renovate.json
(gomod manager + pinned-tool custom managers).

Drop stale bypassnro.stensel.nl / Stensel8/bypassnro references; everything is
bypassnro.thectic.nl and Thectic-NL/BypassNRO now.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings September 2, 2026 09:08
@Stensel8 Stensel8 self-assigned this Sep 2, 2026

Copilot AI 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.

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

@Stensel8
Stensel8 merged commit a6830af into main Sep 2, 2026
6 checks passed
@Stensel8
Stensel8 deleted the chore/align-cicd-with-thectic branch September 2, 2026 09:08
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

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