Repository navigation
refactor(template): organize runtime assets into subdirectories - #926
Merged
Merged
Conversation
homelab-agent-bot
Bot
force-pushed
the
refactor/template-asset-layout
branch
from
September 16, 2026 20:43
1734a55 to
60d9333
Compare
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.
Summary
scripts/config//scripts/*runtime paths unchangedWhy
The template root currently mixes OpenTofu source with the shell and native configuration files it packages. Grouping those assets by kind makes the source layout navigable without changing the generated ConfigMap or workspace behavior. The temporary watchdog copy keeps the existing fixture workflow valid while the shipped and unshipped changes pass CI independently.
Validation
pre-commit run --all-filestofu init -lockfile=readonlytofu validatetflint --config=../../../.tflint.hclFollow-up
The stacked support-layout PR moves the unshipped watchdog fixture and updates its workflow and documentation. The repository's commit taxonomy requires shipped template changes and unshipped CI changes to land in separate PRs.