Skip to content
This repository was archived by the owner on Sep 19, 2024. It is now read-only.

Commit 7570f54

Browse files
authored
docs: update QA docs
1 parent 2a7d379 commit 7570f54

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -180,13 +180,13 @@ For payment to work in your local instance, ubiquibot must be set up in a Github
180180

181181
## How to QA any additions to the bot
182182

183-
Make sure you have your local instance of ubiquibot running.
184-
185-
1. Fork the ubiquibot repo and add your local instance of ubiquibot to the forked repository.
186-
2. Enable Github action running on the forked repo and allow `issues` on the settings tab.
187-
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.
188-
4. Describe carefully the steps taken to get the feature working, this way our team can easily verify.
189-
5. Link that QA issue to the pull request as indicated on the template before requesting a review.
183+
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
184+
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
185+
3. Install the [QA app](https://github.com/apps/ubiquibot-qa) into your forked ubiquibot repository
186+
4. Solve one of the [issues](https://github.com/ubiquity/ubiquibot/issues) and commit changes to the `development` branch of your forked ubiquibot repository
187+
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
188+
6. Describe carefully the steps taken to get the feature working, this way our team can easily verify
189+
7. Link that QA issue to the pull request as indicated on the pull request template before requesting a review
190190

191191
## How to create a new release
192192

0 commit comments

Comments
 (0)