From e87c36de2cc267cbdeec976153f984fd578d4ad1 Mon Sep 17 00:00:00 2001 From: lilydu Date: Wed, 12 Feb 2025 13:52:03 -0800 Subject: [PATCH] fix README images and instructions --- js/samples/04.ai-apps/j.ossDevOpsAgent/README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/js/samples/04.ai-apps/j.ossDevOpsAgent/README.md b/js/samples/04.ai-apps/j.ossDevOpsAgent/README.md index cd58b6e4c..53cf09dcc 100644 --- a/js/samples/04.ai-apps/j.ossDevOpsAgent/README.md +++ b/js/samples/04.ai-apps/j.ossDevOpsAgent/README.md @@ -8,9 +8,7 @@ This sample requires creating an OAuth Connection in Azure Bot Service, which pr ## Interacting with the Agent -You can start to interact with this agent by sending it a message. - -Once you are ready to authenticate, send a message containing the keyword `login`. You will then be forwarded to the GitHub Oauth portal on the browser. +You can start to interact with this agent by sending it a message. Tihs will automatically prompt the login flow, where you will be forwarded to the GitHub Oauth portal on the browser. The agent has three primary capablities (for 1 repo): @@ -85,8 +83,8 @@ The `payload URL` is equal to your `BOT_ENDPOINT` in the `env/.env.local` file, The final settings configured should follow a similiar format: -![Repository Webhook Setup](/assets/webhook-settings.png) +![Repository Webhook Setup](assets/webhook-settings.png) -![Webhook Pull Request Events](/assets/oauth-webhook-events.png) +![Webhook Pull Request Events](assets/oauth-webhook-events.png) Make sure to hit save, and that the webhook is checked off as `Active`. Now your agent is ready to go! \ No newline at end of file