For more information jump to a section below.
|Branch||Description||Build Status||Coverage Status||Windows Bot Test Status||Linux Bot Test Status||Browser Functional Tests|
|Main||4.14.* Preview Builds|
To view package interdependencies, see the dependency graph.
To get started building bots using the SDK, see the Azure Bot Service Documentation.
The Bot Framework Samples includes a rich set of samples repository.
If you want to debug an issue, would like to contribute, or understand how the Bot Builder SDK works, instructions for building and testing the SDK are below.
Clone a copy of the repo:
git clone https://github.com/microsoft/botbuilder-js.git
Change to the SDK's directory:
Install the prerequisites.
Then use the following command to build the SDK.
Use the following command to run the unit tests.
prep-test.cmd command is run to install test keys and start the Azure Storage Emulator if its installed. Any unit tests needing test keys or the storage emulator are designed to be skipped if their dependencies are missing so most developers won't need to worry about running this command.
If you have a need to re-generate the LUIS or connector clients using the latest swagger you'll need to install
autorest (requires Node 7.10.0 or higher), which you can do with the following command.
yarn global add global autorest
Below are the various channels that are available to you for obtaining support and providing feedback. Please pay carful attention to which channel should be used for which type of content. e.g. general "how do I..." questions should be asked on Stack Overflow, Twitter or Gitter, with GitHub issues being for feature requests and bug reports.
Github issues should be used for bugs and feature requests.
Stack Overflow is a great place for getting high-quality answers. Our support team, as well as many of our community members are already on Stack Overflow providing answers to 'how-to' questions.
The Gitter Channel provides a place where the Community can get together and collaborate.
We welcome contributions and suggestions. Please see our contributing guidelines for more information.
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at [email protected]. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License.