chore: Hide the Docfx templates folder from VS project tree #9554
Conversation
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
jwfx
force-pushed
the
exclude-templates-project-tree
branch
from
cc5c4d4 to
7017ed7
Compare
yufeih
added
the
bug-fix
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9554 +/- ##
==========================================
- Coverage 71.36% 71.35% -0.02%
==========================================
Files 558 558
Lines 24032 24032
Branches 4176 4176
==========================================
- Hits 17151 17148 -3
- Misses 5782 5784 +2
- Partials 1099 1100 +1 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hide the Docfx templates folder from VS project tree, via docfx.app.props file as workaround until the issue is resolved from NuGet side.
Credits for workaround: NuGet/Home#4856 (comment)
Fixes #9549