better way to ref docs.ms.com #2539
Merged
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
|
Yes, it's worth doing, but for xref links the new VS Code Docs Authoring Pack xref link generation function is much better than the xrefgen site. |
smitpatel
approved these changes
Jul 28, 2020
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.
This is a better way to reference https://docs.microsoft.com/ documents. Even better is to use @guardrex awesome tool https://xrefgen.azurewebsites.net/?handler=GetSearchResults and click the copy button.
cc @tdykstra @scottaddie to see if this PR is worth doing. I think so because lots of folks look at current doc on how to do updates, new docs, etc.