fix: Use docfx.json as replacement target #1547
Closed
Conversation
This file contains 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
egil
previously approved these changes
Sep 11, 2024
|
Same "problem" as #1548 The "downgrade" issue |
linkdotnet
force-pushed
the
fix-1546
branch
from
a510d84
to
cda5e48
Compare
|
Have to integrate #1548 as our .net 9 builds are failing. |
|
I will close this PR and put this bid into the "fix .net 9" branch. I don't think it is super urgent to get this out and we can wait until the next release. |
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.
At some point in the past we moved the footer from the template file (
footer.temp.partial) to inside the docfx.json due to their updated master template file.Fixes #1546