[llvm] Fix #65890: Update the bot message to use github pull requests (PR #65914)

[via llvm-commits]

https://github.com/Da-Viper created https://github.com/llvm/llvm-project/pull/65914:

None

>From 9c17bb1ead6e8433ba0cebfe264ebb133c59ee81 Mon Sep 17 00:00:00 2001
From: Ezike Ebuka <yerimyah1 at gmail.com>
Date: Sun, 10 Sep 2023 22:39:18 +0100
Subject: [PATCH] Fix #65890: Update the bot message to use github pull
 requests

---
 llvm/utils/git/github-automation.py | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/llvm/utils/git/github-automation.py b/llvm/utils/git/github-automation.py
index 7df20ea8457155b..77f1b1f2aab24e9 100755
--- a/llvm/utils/git/github-automation.py
+++ b/llvm/utils/git/github-automation.py
@@ -23,17 +23,15 @@
 
 This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:
 
-  1) Assign the issue to you.
+  1) In the comments of the issue, request for it to be assigned to you.
   2) Fix the issue locally.
   3) [Run the test suite](https://llvm.org/docs/TestingGuide.html#unit-and-regression-tests) locally.
     3.1) Remember that the subdirectories under `test/` create fine-grained testing targets, so you can
          e.g. use `make check-clang-ast` to only run Clang's AST tests.
   4) Create a `git` commit
   5) Run [`git clang-format HEAD~1`](https://clang.llvm.org/docs/ClangFormat.html#git-integration) to format your changes.
-  6) Submit the patch to [Phabricator](https://reviews.llvm.org/).
-    6.1) Detailed instructions can be found [here](https://llvm.org/docs/Phabricator.html#requesting-a-review-via-the-web-interface)
-
-For more instructions on how to submit a patch to LLVM, see our [documentation](https://llvm.org/docs/Contributing.html).
+  6) Submit the pull request in the [github repository](https://github.com/llvm/llvm-project/pulls).
+    6.1) Detailed instructions can be found [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)
 
 If you have any further questions about this issue, don't hesitate to ask via a comment on this Github issue.
 """