Open source task submission #2917
Merged
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.
Assignment Proposal
Title
Fixing Go's documentation site: to support
subdirectoryfield ingo-importmeta tagsNames and KTH ID
Deadline
Category
Description
We plan to contribute to the Go toolchain ecosystem by fixing an issue where Go's package documentation fails to be fetched when the package is located in a subdirectory of a repository.
Putting Go's package under a subdirectory is supported since Go 1.25. However, there is an issue with the documentation system; it failed to support this new feature.
We perform this by
subdirectoryfield ingo-importmeta tags (introduced in Go 1.25) can be used.The repository (
edv1n/go-get-subdirectory-test) hosts Go module in subdirectories (gopkg/andgopkg/sub/) and serves proper meta tags via GitHub Pages (edv1n.github.io/go-get-subdirectory-test).The goal is to help Go developers and the broader DevOps community adopt the new feature that a Go package can be located inside a directory of a repo, by fixing the Go documentation site to support this new feature.
Relevance
This proposal is relevant to DevOps because package management and dependency resolution are essential for build reproducibility, CI/CD pipelines, and continuous delivery. By providing a reference repo on how Go's module system handles subdirectories and import paths, and fixing the documentation site to support this new feature, we improve developer workflow, reduce integration errors, and support sustainable dependency management in DevOps practices.
Submission
We proposed this task because we found an issue reported on Go's repo that the documentation system is not resolving packages properly, if the package is served with Go's 1.25 new sub-directory feature for resolving a module path.
We have designed a repo to experiment with this new Go feature. It utilizes GitHub Page to serve the Go's import tag, so that Go can import our experiment packages properly. For details, please refer to the README in the repo.
We have created a PR, # 113 on their mirror repo on GitHub golang/pkgsite. Here is what we have done with our contribution:
This contribution is relevant to the project's roadmap as the feature has already been released. However, the documentation system hasn't caught up with this new feature; as a result, developers cannot read the documentation of packages using this new feature.