Initialize Hugo config directory and split module mounts - #945
Conversation
| target = "content/community/contribute/guidelines" | ||
| files = ["! guidelines-adapters.md"] | ||
|
|
||
| # This file is automatically generated by tools/sync_tutorials.py |
There was a problem hiding this comment.
This file is not provided in this PR.
There was a problem hiding this comment.
This file along with the workflow will need some refining/triage so i will raise a PR for it asap
There was a problem hiding this comment.
FYI: Maybe I am missing something, but it looks like this PR is still pending.
There was a problem hiding this comment.
Do the go.mod and go.sum need to be in the repository? Since they are generated, the CI should generate them.
There was a problem hiding this comment.
CI will update them , like whenever there is a new commit in the imported repositories the CI will update them to the latest commit , but will not generate the files entirely
Example : MuhammadAashirAslam@a84c126
There was a problem hiding this comment.
So, the files need to be there with some initial state, but the updates will not need to be continuously updated in the repository, correct?
github-project-automation
Bot
moved this from Needs review
to Done
in GSoC 2026: Website modernization
2 participants
Initializing the hugo configuration folder
Created hugo.toml to house core site variables, parameters, and layout defaults (translating _config.yml scopes).
Created module.toml to securely isolate all repository mounts. This is full replacement of subprojects.rb.
go.mod lists every imported repository as a Hugo Module and pins each to a specific commit-derived version.
go.sum stores the verified checksums for those exact module versions, ensuring Hugo downloads the expected source content reproducibly.
Note: This dividing of the hugo.toml configuration file was supported by hugo so I did this , this makes the files have a cleaner look but if we want to revert back to a single file we can do that .