Issue resolution updates #391
Conversation
Addresses issue #196 *On my Surface Book keyboard + and = are the same key, but this may not be the case for all keyboard layouts.
|
Docs Build status updates of commit 4fb927f:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| TerminalDocs/command-line-arguments.md | View | Details | |
| TerminalDocs/new-terminal-arguments.md | View | Details | |
| TerminalDocs/customize-settings/actions.md | 💡Suggestion | View | Details |
| TerminalDocs/panes.md | ✅Succeeded | View |
TerminalDocs/command-line-arguments.md
- Line 48, Column 106: [Warning-file-not-found]
Invalid file link: './actions.md'.
TerminalDocs/new-terminal-arguments.md
- Line 0, Column 0: [Warning-h1-missing]
H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
TerminalDocs/customize-settings/actions.md
- Line 1107, Column 2: [Suggestion-column-header-missing]
Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
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 the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
|
Docs Build status updates of commit 0c814fd:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| TerminalDocs/command-line-arguments.md | View | Details | |
| TerminalDocs/new-terminal-arguments.md | View | Details | |
| TerminalDocs/customize-settings/actions.md | 💡Suggestion | View | Details |
| TerminalDocs/get-started.md | ✅Succeeded | View | |
| TerminalDocs/panes.md | ✅Succeeded | View |
TerminalDocs/command-line-arguments.md
- Line 48, Column 106: [Warning-file-not-found]
Invalid file link: './actions.md'.
TerminalDocs/new-terminal-arguments.md
- Line 0, Column 0: [Warning-h1-missing]
H1 is required. Use a single hash (#) followed by a space to create your top-level heading.
TerminalDocs/customize-settings/actions.md
- Line 1107, Column 2: [Suggestion-column-header-missing]
Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
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 the docs.microsoft.com contributor guides
- Post your question in the Docs support channel
|
Docs Build status updates of commit 3258a40:
|
|
Docs Build status updates of commit ffa1f52:
|
|
Overall this looks good. I just had some syntax suggestions and I'm not sure the bottom section of the Settings.json blurb on the Get Started page is needed. :) |
Co-authored-by: Kayla Cinnamon <cinnamon@microsoft.com>
Co-authored-by: Kayla Cinnamon <cinnamon@microsoft.com>
Co-authored-by: Kayla Cinnamon <cinnamon@microsoft.com>
|
Docs Build status updates of commit b8b7b92: ✅ 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:
|
|
Docs Build status updates of commit 69ba53b: ✅ 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:
|
|
Docs Build status updates of commit eb0947d: ✅ 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:
|
No description provided.