-
Couldn't load subscription status.
- Fork 156
Fix broken links #343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken links #343
Conversation
|
@mrlacey can you please try updating the master branch into your own branch? |
|
Docs Build status updates of commit f324cc8:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/platform-specific/PlatformSpecificDifferencesGenerator.md | View | Details | |
| docs/helpers/Colors.md | ✅Succeeded | View | |
| docs/helpers/StorageFiles.md | ✅Succeeded | View | |
| docs/helpers/Streams.md | ✅Succeeded | View | |
| docs/helpers/ThemeListener.md | ✅Succeeded | View | |
| docs/helpers/WeakEventListener.md | ✅Succeeded | View | |
| docs/services/Linkedin.md | ✅Succeeded | View | |
| docs/services/MicrosoftTranslator.md | ✅Succeeded | View |
docs/platform-specific/PlatformSpecificDifferencesGenerator.md
- Line 49: [Warning-InvalidFileLink]
Invalid file link:(~/platform-specific/platformspecificanalyzer).
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching in the Docs contributor and Admin Guide
- See the frequently asked questions
- Post your question in the Docs support channel
|
Triggering another doc check pass to make sure validation went away. |
|
Docs Build status updates of commit f324cc8:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/platform-specific/PlatformSpecificDifferencesGenerator.md | View | Details | |
| docs/helpers/Colors.md | ✅Succeeded | View | |
| docs/helpers/StorageFiles.md | ✅Succeeded | View | |
| docs/helpers/Streams.md | ✅Succeeded | View | |
| docs/helpers/ThemeListener.md | ✅Succeeded | View | |
| docs/helpers/WeakEventListener.md | ✅Succeeded | View | |
| docs/services/Linkedin.md | ✅Succeeded | View | |
| docs/services/MicrosoftTranslator.md | ✅Succeeded | View |
docs/platform-specific/PlatformSpecificDifferencesGenerator.md
- Line 49: [Warning-InvalidFileLink]
Invalid file link:(~/platform-specific/platformspecificanalyzer).
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching in the Docs contributor and Admin Guide
- See the frequently asked questions
- Post your question in the Docs support channel
|
Docs Build status updates of commit 14870af: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
What changes to the docs does this PR provide?
Just fixes some broken links (Found while investigating #340)
PR Checklist
Please check if your PR fulfills the following requirements:
masterfor new features,livefor typos/improvements)Other information