From 7570f54f6aefcf74a1957d6af923df6a1b5ebe9e Mon Sep 17 00:00:00 2001
From: rndquu <119500907+rndquu@users.noreply.github.com>
Date: Mon, 23 Oct 2023 19:02:36 +0300
Subject: [PATCH 1/2] docs: update QA docs

---
 README.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index e8d09c845..d7eb5f4af 100644
--- a/README.md
+++ b/README.md
@@ -180,13 +180,13 @@ For payment to work in your local instance, ubiquibot must be set up in a Github
 
 ## How to QA any additions to the bot
 
-Make sure you have your local instance of ubiquibot running.
-
-1. Fork the ubiquibot repo and add your local instance of ubiquibot to the forked repository.
-2. Enable Github action running on the forked repo and allow `issues` on the settings tab.
-3. Create a [QA issue](https://github.com/ubiquibot/staging/issues/21) similar to this where you show the feature working in the forked repo.
-4. Describe carefully the steps taken to get the feature working, this way our team can easily verify.
-5. Link that QA issue to the pull request as indicated on the template before requesting a review.
+1. [Create](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch) a new github organization for testing purposes
+2. [Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo#forking-a-repository) the [ubiquibot](https://github.com/ubiquity/ubiquibot) repository into your test organization
+3. Install the [QA app](https://github.com/apps/ubiquibot-qa) into your forked ubiquibot repository
+4. Solve one of the [issues](https://github.com/ubiquity/ubiquibot/issues) and commit changes to the `development` branch of your forked ubiquibot repository
+5. Create a QA issue similar to [this](https://github.com/web4er/ubiquibot/issues/38) where you show how the feature is working in the forked ubiquibot repository
+6. Describe carefully the steps taken to get the feature working, this way our team can easily verify
+7. Link that QA issue to the pull request as indicated on the pull request template before requesting a review
 
 ## How to create a new release
 

From 9f583c3dc7896d274c4643ca8bf9908ece690da7 Mon Sep 17 00:00:00 2001
From: rndquu <119500907+rndquu@users.noreply.github.com>
Date: Sat, 11 Nov 2023 00:04:14 +0300
Subject: [PATCH 2/2] docs: update README.md

---
 README.md | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index d7eb5f4af..c0249a0be 100644
--- a/README.md
+++ b/README.md
@@ -180,13 +180,12 @@ For payment to work in your local instance, ubiquibot must be set up in a Github
 
 ## How to QA any additions to the bot
 
-1. [Create](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch) a new github organization for testing purposes
-2. [Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo#forking-a-repository) the [ubiquibot](https://github.com/ubiquity/ubiquibot) repository into your test organization
-3. Install the [QA app](https://github.com/apps/ubiquibot-qa) into your forked ubiquibot repository
-4. Solve one of the [issues](https://github.com/ubiquity/ubiquibot/issues) and commit changes to the `development` branch of your forked ubiquibot repository
-5. Create a QA issue similar to [this](https://github.com/web4er/ubiquibot/issues/38) where you show how the feature is working in the forked ubiquibot repository
-6. Describe carefully the steps taken to get the feature working, this way our team can easily verify
-7. Link that QA issue to the pull request as indicated on the pull request template before requesting a review
+1. [Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo#forking-a-repository) the [ubiquibot](https://github.com/ubiquity/ubiquibot) repository
+2. Install the [QA app](https://github.com/apps/ubiquibot-qa) into your forked ubiquibot repository
+3. Solve one of the [issues](https://github.com/ubiquity/ubiquibot/issues) and commit changes to the `development` branch of your forked ubiquibot repository
+4. Create a QA issue similar to [this](https://github.com/web4er/ubiquibot/issues/38) where you show how the feature is working in the forked ubiquibot repository
+5. Describe carefully the steps taken to get the feature working, this way our team can easily verify
+6. Link that QA issue to the pull request as indicated on the pull request template before requesting a review
 
 ## How to create a new release