Fix broken SupplementalAttribute cross-reference in EmissionsData docstring#1687
Closed
Copilot wants to merge 2 commits into
Closed
Fix broken SupplementalAttribute cross-reference in EmissionsData docstring#1687Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job build
Fix broken SupplementalAttribute cross-reference in EmissionsData docstring
May 31, 2026
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
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.
The
buildCI job was failing becauseInfrastructureSystems.SupplementalAttributeno longer carries a docstring, causing Documenter.jl to error when resolving the bare@reflink in theEmissionsDatadocstring included via@autodocsindocs/src/api/public.md.Changes
src/emissions_data.jl: Changed[SupplementalAttribute](@ref)→[SupplementalAttribute](@ref supplemental_attributes), linking to the explanation page anchor instead of an API docstring — consistent with how other docs in this repo already reference the concept.