[TTK related]Update what-are-webhooks-and-connectors.md

Add Teams Toolkit notes to following pages:
what are webhook and connectors
add incoming webhooks
send proactive messages.
provide related samples in above pages.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
88
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 706f836:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 276: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 535: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 276: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 535: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
88
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit feb4b0d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 287: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 546: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 287: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 546: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 276: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 535: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 276: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 535: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
18
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
88
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 41fc7db:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 19, Column 243: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 363: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 476: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 243: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 363: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 476: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 287: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 546: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 287: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 546: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 276: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 535: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 276: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 535: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
18
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
88
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 50cd64c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 19, Column 243: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 363: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 476: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 243: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 363: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 476: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 164: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 623: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 164: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 623: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 276: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 535: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 276: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 535: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
18
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
18
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 3f052bc:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 19, Column 243: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 363: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 476: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 243: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 363: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 476: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 164: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 622: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 164: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 622: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 170: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 628: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 170: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 628: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Docs Build status updates of commit 36801be:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 19, Column 243: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 363: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 476: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 243: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 363: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 476: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 164: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 622: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 164: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 622: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 170: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 628: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 170: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 628: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
18
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 40f7baf:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 19, Column 71: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 567: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 71: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 567: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 164: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 622: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 164: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 622: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 170: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 628: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 170: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 628: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
18
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
18
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit b1de5aa:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: CannotMergeCommit] Cannot merge commit b1de5aaab2f03a829853c167c10cca80d5f75be6 in branch zyxiaoyuer-update-webhook of repository https://github.com/MicrosoftDocs/msteams-docs into branch main (commit db91b1e8b23db2067651265b920635417dac64fe). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
96
3
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 4d64da5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/what-are-bots.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 20, Column 69: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20, Column 565: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20, Column 69: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 20, Column 565: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/bots/what-are-bots.md

Line 12, Column 31: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 12, Column 131: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 12, Column 31: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' will be broken in isolated environments. Replace with a relative link.
Line 12, Column 131: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 164: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 622: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 164: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 622: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 170: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 628: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 170: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 628: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 5f2f75f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/what-are-bots.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 20, Column 69: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20, Column 565: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20, Column 69: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 20, Column 565: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/bots/what-are-bots.md

Line 12, Column 31: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 12, Column 131: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 12, Column 31: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-bot' will be broken in isolated environments. Replace with a relative link.
Line 12, Column 131: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 164: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 622: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19, Column 164: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 19, Column 622: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 170: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 628: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 15, Column 170: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot' will be broken in isolated environments. Replace with a relative link.
Line 15, Column 628: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/toolkit/teams-toolkit-fundamentals' will be broken in isolated environments. Replace with a relative link.

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 or suggestions 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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 47b667c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:white_check_mark:Succeeded
View

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:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 5f99bd5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:warning:Warning
View
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

Line 19, Column 560: [Warning: file-not-found - See documentation] Invalid file link: '../../../toolkit/teams-toolkit-fundamentals.md'.

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 171: [Warning: file-not-found - See documentation] Invalid file link: '../../sbs-gs-notificationbot.yml'.
Line 15, Column 560: [Warning: file-not-found - See documentation] Invalid file link: '../../../toolkit/teams-toolkit-fundamentals.md'.

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 or suggestions 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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 35360ce:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:white_check_mark:Succeeded
View

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:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

link
:warning:

msteams-platform/bots/what-are-bots.md

link
:warning:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md

link
:warning:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

link
:warning:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit d566a9a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:white_check_mark:Succeeded
View

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:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
89
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit a087c6a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:white_check_mark:Succeeded
View

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:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
93
5
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 43bde18:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:white_check_mark:Succeeded
View

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:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a483b5f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md

Line 15, Column 180: [Warning: file-not-found - See documentation] Invalid file link: '../../sbs-gs-notificationbot.yml'.
Line 15, Column 558: [Warning: file-not-found - See documentation] Invalid file link: '../../toolkit/teams-toolkit-fundamentals.md'.

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 or suggestions 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 guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
95
8
link
:white_check_mark:

msteams-platform/bots/what-are-bots.md
92
6
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
95
4
link
:white_check_mark:

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
93
5
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 07a6f25:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/bots/what-are-bots.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/add-incoming-webhook.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/what-are-webhooks-and-connectors.md
:white_check_mark:Succeeded
View

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:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


chore: Split frontend and backend build parts

Split frontend and backend build parts
Makefile

make will call Makefile in frontend and backend
make run call run in both frontend and backend

Dockerfile

use distroless for run

use non-root user

make binary static

and make it smaller

use node image for frontend build
use caching

remove non-cache build parameter
improve .dockerignore
use docker/dockerfile:1.3 syntax for better caching

For buildah, a patch fixed it... but not yet released :( https://github.com/containers/buildah/pull/3574
For GitHub actions, that's why I added a special action that install buildkit.

@guilhem , I have tried again with an updated podman and I could build it.
However, with docker in my Fedora box I have permissions issues when mounting the cache. Not sure I am doing something wrong or whether it's docker's version (from the moby-engine 20.10.10).
I wonder if the docker related changes will become an issue for other users too. What do you think?
We can also always extract the docker related changes into a new PR and merge the rest, as the Makefile LGTM now.

I wonder if the docker related changes will become an issue for other users too. What do you think?

I tried to do it the "actual way" (it was some kind of challenge too).
But yes, some people without latest buildkit can have problems.

We can also always extract the docker related changes into a new PR and merge the rest, as the Makefile LGTM now.

It sound a really good idea to me :)

We can also always extract the docker related changes into a new PR and merge the rest, as the Makefile LGTM now.

It sound a really good idea to me :)

Thanks @guilhem . Since it was not clear who should do this, do you want to extract the Docker commits into a new PR yourself?
If you don't have time, let me know.

We can also always extract the docker related changes into a new PR and merge the rest, as the Makefile LGTM now.

It sound a really good idea to me :)

Thanks @guilhem . Since it was not clear who should do this, do you want to extract the Docker commits into a new PR yourself? If you don't have time, let me know.

@guilhem , do you have time to split the docker changes out?

We can also always extract the docker related changes into a new PR and merge the rest, as the Makefile LGTM now.

It sound a really good idea to me :)

Thanks @guilhem . Since it was not clear who should do this, do you want to extract the Docker commits into a new PR yourself? If you don't have time, let me know.

@guilhem , do you have time to split the docker changes out?

Working on it :)

@guilhem Awesome! 🥳


Android Gradle Plugin 4.0.0 Incompatible

The current 4.0.0 beta releases eg. 4.0.0-beta04 of AGP isn't compatible with v4.1.0 of this plugin.
When AGP is upgraded to say 4.0.0-beta04  it throws this error
Configuration on demand is an incubating feature.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':analytics'.
> Failed to notify project evaluation listener.
   > com.android.build.gradle.internal.variant.BaseVariantData.getVariantConfiguration()Lcom/android/build/gradle/internal/core/GradleVariantConfiguration;
   > com.android.build.gradle.internal.variant.BaseVariantData.getVariantConfiguration()Lcom/android/build/gradle/internal/core/GradleVariantConfiguration;

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

AGP 4+ has removed internal APIs that is used by this plugin

Now that Android Studio 4.0 is released, have the same issue with AGP 4.0.0.

Released: 4.2.1
But it will not be compatible with earlier versions of AGP :(


Document use of PAT token

We need to use personal access tokens for some actions in e2e tests. We should document what those actions are and what scopes the PAT needs to have, and how to create one.
Why do we need PAT?

push using github.token does not trigger subsequent workflows: https://github.community/t/push-from-action-does-not-trigger-subsequent-action/16854
to create issues in the slsa-framework/slsa-github-generator repo since it's not the same repository.

What scopes do we need:

repo
???

Related to #52

GITHUB_TOKEN in github actions has a rate limit of 1000 request per repo per hour which could be problematic.
https://docs.github.com/en/rest/overview/resources-in-the-rest-api#requests-from-github-actions

We also need scope to create releases.

We also need scope to create releases.

I added creating releases to the list of things we need it for. I think this is covered under the repo scope for the PAT though.

repo is either public read or write, and I never remember which it is. :)

repo scope seems to add a bunch of things for PAT including sub-scopes like repo invites, security events. It's really confusing between PAT scopes and the Github Actions token scopes.


Removed reference to object explorer

Removed reference to object explorer since ADS does not have one

I think the reference to Object Explorer is referring to the schema browser in the Server Viewlet.  The updated description loses a reference to that entry point.  In any case, I think we're going to rewrite the readme this week for to include details for the DACPAC\BACPAC functionality.

Well if it is referring to the schema browser, note that that  has no option for import/export that I can see.

@gbritton1 there is supposed to be a context menu on the database node in the Server viewlet.  Are you not seeing that?

No I don't see it there.  Note that to get the image, I right-clicked on a
database name.  The image is the context menu that popped up.
On Mon, Dec 10, 2018 at 7:29 PM Karl Burtram<EMAIL_ADDRESS>wrote:

@gbritton1 https://github.com/gbritton1 that looks like the context
menu for the Connection node. The Import menu is expected to be on the
Database node, under the Databases folder. Do you not see it there?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/azuredatastudio/pull/3463#issuecomment-446027088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALsfeDZGgEx14evc-pOGe2VxLBhTJJlPks5u3vx-gaJpZM4ZDEAF
.

--
Gerald Britton, MCSE-DP, MVP
LinkedIn Profile: http://ca.linkedin.com/in/geraldbritton

@gbritton1 I think that what's happening is that your connection is to a database, where as if you create the connection to the server (i.e. don't provide a database name in the connection dialog), then you get a Databases folder with child database nodes.  I think the context menu only shows on the child database nodes.
This seems like a bug since the context menu should show on both the connection and the sub DB nodes, since the dialog prompts for the connection details in any case.  I'll open an issue for that.


Remove unused code

We can use vulture to identify unused functions and classes throughout QSIPrep. I ran it on both XCP-D and ASLPrep when I started maintaining them, and I've found it very useful.

Here are results from the current version (master at 527ef59).
vulture.txt

I think I can close this since we managed The Great Split.


toolchain: gcc: check if __weak is defined

Avoid build conflict when __weak is defined by someone else.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

This is a cleaner fix for #8563

Tested locally. This does remove the warnings mentioned in #8563.


Hexagon 685/690 wrong SoC examples for QCS610/QCS410 on TensorFlow Lite Hexagon delegate

On this page:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/g3doc/performance/hexagon_delegate.md
It states that QCS610, QCS410 are SoC examples for Hexagon 690. However, according to Qualcomm's product info:
https://www.qualcomm.com/products/qcs610
Both SoC QCS610 and QCS410 contain Hexagon 685 rather than Hexagon 690.

@karimnosseir could you review this suggestion?

@tomchen1000  Thanks for the feedback. I've reached to QC to confirm and didn't hear back from them yet.
Thanks


Update "Design & impl" section in book.

The section is out of date in many parts. It should be revisited to make sure it reflects the current design and implementation.
https://defmt.ferrous-systems.com/design
For the moment it would be good to add a header to every page which warns about it being potentially outdated. Maybe > ⚠ The design and implementation chapter is outdated ⚠.

Will sort this


dead cells or old movements take over the map

currently the more u play the map get populated with old static cells and its hard to see the live -real time cells.
is this new problem because the updates going on site? i know u told me  script  not working anymore but it was normal until 3 days ago .
can u clear the map ?
many thanks

@aero9 Yes, that is another bug

ok thanks for letting me know.


Support DNX based WebJobs

FYI - changes in dnvm.ps1 match changes here https://github.com/aspnet/dnvm/pull/396 so if they accept that PR, we won't need a special version of dnvm.ps1

Rest of code looks good to me - no further comments :)

Nice :)


Does it really work?

Bla bla bla

If you want to test it, you should probably check out the demo.


Superscript symbols are not typesetted

All superscript symbols don't appear on the autocompletion list after typing \^ and are not typesetted after manually writing e.g. ^2 among the others.

I believe this has been fixed on the master branch (it works for me there)
@one-more-minute , do we need to tag this guy?

Would be great to do a patch release – I'm releasing julia-client today anyway so I'll go ahead and get it done.

aaaand it's done.

Wow, that was fast! Excellent! Thank you!

No problem :)


Rm TC internals from thermo state computation

Peel off PR from #960

bors r+

bors r+

bors r+


Question about a pipeline design pattern

Hi!
I'm looking for a pipeline-based design pattern where each side-effect is run through a yield. Something like
function doSomething()
{
  if ($whatever) {
    yield $io->db->query('UPDATE bla ...');
  } else {
    yield $io->file->write($filename, $data);
  }
  // More logic...
}

(Please disregard undefined variables.)
The point would be that all side-effects that do not depend on the result of the side-effect can be executed concurrently. So IO concurrency would be the default behaviour. Is this something that can be achieved with Amphp?

Hey @olleharstedt, yes, that's definitely possible. The implementation will depend on the requirements, obviously. For a smaller pipeline you might be able to analyze the dependencies manually and write the code down, but for a larger or dynamic set of tasks, it'll be easier to define a framework around the tasks that handles priorization / ordering. https://github.com/dbalabka/dag might be a good starting point.

Hm, ordering should be FIFO, as expected by the flow of the code. So a graph of priority or similar wouldn't be needed (as of what I plan right now). What's needed is that the controlling code runs each side-effect and returns to logic before it's finished. Kind of like this line:
list($result1, $result2) = yield $promises; // Both queries execute simultaneously. Wait for both to finish

https://github.com/amphp/mysql/blob/master/examples/4-multi-rows.php#L23
But yield should not wait.


Question:  If using only Custom MDT-based Rollups, is it possible to avoid queries of config sObjects?

In a new org with only Custom MDT-based rollups, it appears that DLRS still queries the sObject-based config in Lookup Rollup Summary object.  Is it possible to configure DLRS to ignore all sObject-based config and only look at Custom MDT rollups?  It would reduce the number of SOQL queries in complex testing scenarios.

Its not possible, but, i guess we could add a custom metadata/object setting for this easily. I'll flag this as an enhancement. Would be a pretty easy change to the selector class methods tbh.


Image resizing doesn't work on every computer

Microsoft PowerToys version
v0.74.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Image Resizer
Steps to reproduce

Choosing images in explorer
Clicking right - Contextmenu
Choosing 'Resize'
Nothing happens

✔ Expected Behavior
Appearing Dialog for size and overwritiing-options
❌ Actual Behavior
Nothing
Other Software
No response

A bug report from the PC where nothing happens would be useful:
/bugreport

Thank you for your response!
Here comes the zipfile with the report:
PowerToysReport_2023-10-17-14-40-41.zip

Is there something new with this issue?

I do not know. I am not sure who would be working on this utility and if the bug was reproduced or not.

I still need a solution there...

Are you still experiencing this issue? /needinfo


[HOTFIX] Fixes git dir being checked too early

Deactivation of the plugin could not be checked as a missing git dir was already stopping the process

Thanks ;)

I changed it around a bit to have the detection stuff still in one place
        if ($this->shouldExecutionBeSkipped()) {
            return;
        }
        $this->detectConfiguration();
        $this->detectCaptainExecutable();
        $this->detectGitDir();

        if ($this->dotGit->isAdditionalWorktree()) {
            $this->displayGitWorktreeInfo();
            return;
        }

I released version 1.0.1 with the fix.
Thanks again :)


Dockerfile: Use https everywhere

Changed plain http downloads to https ones.
If it actually IS safe to download these files via plain http, please pardon my ignorance. An explanation would be appreciated. I'm not familiar with the inner workings of .debs / apt, but this doesn't seem right to me.

@j2L4e No issue on the CI, so I guess we're good 👍


Add a comment section

It would be realy nice to hace the abillity to create a discussion directly on the blog post.

This is a great idea as I know running my own blog that people sometimes add things into the comments that make the post even better. I'm exploring something to do this.

Comments have been added @avrahamcool https://aurelia.io/blog/2024/12/19/new-aurelia-website/

wow.. that was quick.
Thanks a lot..
that goes to show how the new site was worth it :)


Redirect Lighthouse pages to new resources

What's changed, or what was fixed?

Redirect from the old scoring docs to the new one on web.dev
Simplify the TOC entirely and point to the new web.dev docs

At this point the audit docs on DGC are outdated/deprecated and we now consider all the web.dev locations to be the canonical resources.
Target Live Date: whenever

[ ] This has been reviewed and approved by (NAME)
[ ] I have run npm test locally and all tests pass.
[ ] I have added the appropriate type-something label.
[ ] I've staged the site and manually verified that my content displays correctly.

CC: @petele

:+1:


Add docs for Abstract Infer classes

Addresses #1683. My last PR, I don't want to spam PR during the end of the year. Happy new year! :dancer:

@eb8680 can you please confirm that we want to add docs to all these things? I recall you wanted to remove things, and we should avoid adding docs to any classes or methods planned for deprecation.

confirm that we want to add docs to all these things

Since the methods documented in this PR are already in 0.3, I'm fine with merging this for now.  We can revisit later if we decide to do a cleanup release.


opt:in not working

Hi
My webapp is fully RTL so I don't need to flip my styles, I just need mui's own components to flip. I'm using jss.use(rtl({ opt: 'in' })); as mentioned in docs. But that makes no difference and flipping persists.

can you show me more code? Something I can reproduce the issue with.

@alitaheri
import React from 'react';
import { MuiThemeProvider } from '@material-ui/core/styles';
import CssBaseline from '@material-ui/core/CssBaseline';
import JssProvider from 'react-jss/lib/JssProvider';
import { create } from 'jss';
import rtl from 'jss-rtl';
import { Provider } from 'react-redux'
import { jssPreset } from '@material-ui/core/styles';

// Configure JSS
const jss = create({ plugins: [...jssPreset().plugins] });
jss.use(rtl({ opt: 'out' }));

...

render() {
    return (
        <JssProvider
            jss={jss}
            registry={this.pageContext.sheetsRegistry}
            generateClassName={this.pageContext.generateClassName}
        >
            <MuiThemeProvider
                theme={this.pageContext.theme}
                sheetsManager={this.pageContext.sheetsManager}
            >
                <Component pageContext={this.pageContext} {...pageProps} />
            </MuiThemeProvider>
        </JssProvider>
    )
}

@pooriamo withStyles has it's own logic regarding jss-rtl this is related to material-ui.
https://github.com/mui-org/material-ui/blob/master/packages/material-ui/src/styles/withStyles.js#L244
I don't know how it can be fixed, to be honest. but whatever the fix is, it's not related to this library. you need to open another issue (or PR) against material-ui


release version 0.0.3

done

the 0.0.3 version removes the camel to snake and also add backward compatibility


Adding member functions

Add any 10 valid member functions with legitimate prototypes that are not present so far.

I'd like to work on this

helloo, may I work on this as well?

@shreya1010svg , can I contribute to this as well


DNM: Refactor takeover

Work-in-progress fix for #1634.

I'm closing this since we merged https://github.com/ceph/ceph-ansible/pull/1727, feel free to re-open for potential improvements.


Movie's listed as missing even though none are Owned

Describe the bug
I have two movies that are showing as missing in a library however those are the only two movies in their collection and neither is showing as owned in that library. I suspect it's because they are in a different library, but both are owned in that library, so not sure why they are showing as missing in a different library. I believe one of them was originally in this library before being moved to the proper library, so maybe when GAPS scanned the plex library the movie was no longer there, but it didn't remove the entry from the DB?
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Gaps Version [e.g. 22] v0.10.4

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Gaps Version [e.g. 22]

Additional context
Add any other context about the problem here.

It does appear to be something stored in one of GAPS local db's, I found a few other movies in my movies library where one was originally in that library before being moved to the children's movie library and then all movies from that collection were showing as missing in the regular movies library. I did a delete all local data and set everything back up and upon re-scanning those are no longer noted as missing from that library.


Fix CID 1368305: Dereference before null check

#1302

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1352/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1244/ for details.


gear menu: Drop special naming for organization settings menu item.

Removes the special naming ("Manage organization") of the organization settings gear menu item for admins so that it lines up with how we refer to the "Organization settings" UI itself in the help center documentation.

Related PR/discussion https://github.com/zulip/zulip/pull/24134#discussion_r1084637145.

Screenshots and screen captures:

e.g. https://chat.zulip.org/help/review-your-organization-settings

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability

Communicate decisions, questions, and potential concerns.

[x] Automated tests.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Links.

@alya @timabbott This PR is ready for you!

Works for me in manual testing! @timabbott over to you.

Nice, merged, thanks for cleaning this up @drrosa!


supergfxctl-plasmoid: init at 2.0.0

Description of changes
Adds the supergfxctl-plasmoid to Plasma 6 in order to easily use supergfxctl from the system tray (or anywhere you put the widget)
NOTE: There's no binary to test with this, but I have rebuilt my NixOS system and confirmed it works as intended, like it would on any other system (personally observed the same behavior as on Arch and on Fedora)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Currently, the package is not exposed. Please move it to pkgs/by-name/su/supergfxctl-plasmoid/package.nix.
(The old way would have been to add the package to pkgs/top-level/all-packages.nix, but this pattern is being phased out.)

Oh, got it! Sorry!

Like so?

Thank you so much for all your comments! As you can see, it's my first time contributing, so I'll be sure to keep all your suggestions in mind for the future.
That being said, I wasn't aware gcc was part of stdenv, so that's off. Didn't know about the "pname" issue, many of my sources were packages I looked up that are already present in the repos that also used the same structure, but understood! I'll also be sure to keep in mind the better practice for hashes and revisions in mind.
Furthermore, indeed the buildPhase wasn't necessary, but makeFlags (which I actually wasn't even aware of, as an option) didn't appear to be needed either! I've now tested without either and it seems that the defaults are fine. Cmake is still needed though.
Moreover, after other packages I've since been experimenting with had different deps needed, some more necessary and others unnecessary from upstream projects, I've further tested with removing packages from the buildInputs until I arrived at what seems to be the minimal amount, shaving off the rest that seemingly wasn't actually required.
In any case, thank you so much for everything! If there are any further suggestions for improving, be it the package or just the practices for packaging software, I'll be sure to absorb as much as possible!

git rebase -i should give open an editor window:

delete the lines you don't want to include (merge commits should be dropped)
keep the lines you do want to include (the two commits you intend to keep)
reorder the lines to reorder the commits. the first commit is at the top.
replace "pick" with "s" or "squash" to squash the commit into the previous line (this is useful for if you have changes across multiple commits that you want to combine into one big commit)
then save and exit the editor

A more detailed guide is available at https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History

Does that do it? I'm not really sure, the fact that I made the mistake of merging during the PR and having changed the file location threw me off during rebasing

just going to squash merge this


Hookup permission check for scheduler jobs

What changes are proposed in this pull request?
Hookup permission checks in dora worker for scheduler job related endpoints
Why are the changes needed?
To handle permission checking correctly
Does this PR introduce any user facing changes?
N/A

alluxio-bot, merge this please.

alluxio-bot, merge this please.


When will fileRegion be supported?

The io_uring transport does not currently support fileRegion, when will fileRegion be supported?  We are eager to try iouringFileRegion.

@1Jo1 Cloud you mind help to see this issue?

Seems like while sendfile is not directly supported by io_uring itself it is possible to kind of create the same functionality by using splice: https://lwn.net/Articles/810482/

@normanmaurer I don't know much about the Linux kernel. Will netty io_uring consider using splice to implement fileRegion?

I'm not sure there is some gap for netty io_uring  to implement fileRegion by using splice.

Yes .... I just left the comment for the future so I dont forget. I am currently busy but might implement it once I have some cycles.

We really want to try the file region in netty io_uring. If there is no plan for this currently, we can only abandon this plan, thanks very much.

If someone implements it I am happy to review the code... I dont have the cycles atm to do it myself

Hello，Can we have an IoUringChunkedNioFile? I tried it and it doesn't seem difficult.

hi @dreamlike-ocean I think this one to be a better fit outside Netty, which is just a "network" framework.
FileRegion is not indeed a good term because in Netty it implies zero-copy semantic, which is not happening here; I believe that having such async file abstraction in vertx, for example, to be super cool @vietj wdyt?

@franz1981 actually FileRegion should do a zero copy (aka sendfile). We just never did it so far... It should be doable as io_uring supports splice.

@franz1981 actually FileRegion should do a zero copy (aka sendfile). We just never did it so far... It should be doable as io_uring supports splice.

yes ，https://github.com/dreamlike-ocean/PanamaUring/blob/master/panama-uring/src/main/java/top/dreamlike/panama/uring/async/fd/AsyncSplicer.java

Sure we love PRs

Sure we love PRs

Hi! I have submitted a pull request for this requirement. Please  review it.Check if I have correctly understood this requirement.


Add Jekyll Diff Action to the Utility section

https://github.com/David-Byrne/jekyll-diff-action

@David-Byrne your changes have been merged, thanks for your contribution 👍


Problem due to latexindent vs latexindent.pl

This issue is based on my question on tex.stackexchange.com.
Problem: I installed BeautifyLatex in SublimeText 3 on OS X El Capitan . When I tried to save tex file, there was an error:
Error: can't specify None for path argument

I can see that my latexindent was installed by typing which latexindent in the terminal.
$ which latexindent
/Library/TeX/texbin/latexindent

After installing Fix Mac Path and  adding "additional_path_items": ["/Library/TeX/texbin"] in the user settings of BeautifyLatex (kindly suggested by the user r-stein in tex.stackexchange. The error still exists.
Solution: One user (ig0774) in tex.stackexchange.com  suggested to link latexindent.pl to latexindent in the terminal.
$ sudo ln -s /Library/TeX/texbin/latexindent /Library/TeX/texbin/latexindent.pl

After that, BeautifyLatex is up and running. (You need to install Fix Mac Path and add the path first.)
Comments that could be helpful to others: At first, my latexindent does not work at all even in the terminal environment. After cd to the directory /Library/TeX/texbin/ that contains latexindent, I typed perl latexindent and received some error message telling me that YAML::Tiny was missing. After typing the following in the terminal, I managed to make latexindent start working in terminal, but not in the sublime text.
$ sudo cpan App::cpanminus
$ sudo cpanm YAML::Tiny
$ sudo perl -MCPAN -e 'install "File::HomeDir"'

This is very useful information. Do you think you could add something to the readme with a link to this issue?

Done. I added a section for installing beautifylatex on mac in the readme file.

Do you mind submitting a pull request, so that other users who come here might find it?

Of course, I submitted a pull request. Did I do it correctly? I am new to github.

Of course, I submitted a pull request. Did I do it correctly? I am new to github.

Yes, you did it just fine. I can see this section in the readme — https://github.com/ketan/BeautifyLatex#note-for-mac-users.
Thank you very much.


Improve the testing experience when using this library

Expected Behavior
It should be easy to mock dependencies on this library.
Actual Behavior
It is difficult to mock behaviors in this library due to a mix of public / private struct fields and limited use of interfaces in the public interface.
The problem is that this is likely to be a breaking change to the interface and thus would probably need to land in v2.0. This is issue is to track this and to ensure in the next major version testing / mocking is handled better.
#77 spurred this discussion and contains an example of problem.
Environment

Version of Library: v1.0

@devigned I'd like to take a crack at this one to get more familiar with golang and this repo. Is there anything I should be aware of before I dig in?

Well, I am not an active maintainer of this repo any longer. Those duties now fall on @jhendrixMSFT et al, so I'd defer to their team on any guidance / feedback.
This is super Golang'ish background, so please ignore if you are more advanced in Go. Just wanted to provide a bit of a foundation if it isn't there already. I think the biggest thing to grok with Golang vs say C# or Java wrt testing is that an interface in Golang can be defined by anyone and used for duck typing on a type defined in another package where as in Java and C#, a type must implement an interface explicitly at time of type definition. Therefore, defining testing interfaces within a package in Golang isn't really needed. What is needed, is easy access to the structures, fields and Methods defined on types.
If you were to write a simple application using this library, then try to mock out the library like in #77, I think you will quickly see where this becomes a problem with this library.
Perhaps, there's too much encapsulation of types / fields or maybe too much coupling. Either way, I think when you try to mock it, it will become clear where the runtime blows up and where you find yourself feeling less productive having to rewrite a lot of structure just to be able to test.
The changes may cause breaking changes in the API. This is something to try to avoid, if possible. Also, it's something you'd want to call out to @jhendrixMSFT and team.
Happy to help. Please don't hesitate to ping me if I can be of service. Cheers!