From 57ded59148ce6a54b3a1cb9071bfc5925b00694f Mon Sep 17 00:00:00 2001
From: Ruoxuan Wang <52271048+ruowan@users.noreply.github.com>
Date: Wed, 23 Dec 2020 11:34:10 +0800
Subject: [PATCH] Update comment.yml (#12213)

---
 .github/comment.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/comment.yml b/.github/comment.yml
index 2870b7203314..faa44cafad30 100644
--- a/.github/comment.yml
+++ b/.github/comment.yml
@@ -38,7 +38,7 @@
 - rule:
     type: PROpen
     variables:
-      openapiHub: https://openapihub.test.azure-devex-tools.com/
+      openapiHub: https://portal.azure-devex-tools.com
     keywords:
       - "I have reviewed the [documentation](https://aka.ms/ameonboard) for the workflow."
     onOpenedComments: "Hi, @${PRAuthor} Thanks for your PR. I am workflow bot for review process. Here are some small tips. </br> <li> Please ensure to do self-check against checklists in first PR comment.</li> <li> PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging. </li>   <li> For specs comparison cross API versions,  Use [API Specs Comparison Report Generator](${openapiHub}/tools/diff?pr=${owner}/${repo}/${PRNumber})</li>  <li> If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. [How to fix?](https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/ci-fix.md)</li></br> Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com"