summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorwnjuguna <jbworldus@gmail.com>2022-09-15 18:46:57 +0300
committerGitHub <noreply@github.com>2022-09-15 11:46:57 -0400
commite276770ee9efac3a98c3f1116d9cd9c992ca8c9e (patch)
treec384a456e5915bdf8b6b92acee561b2e19748162
parentc7b4a25f9d668c45436ef57503c41bd1abb9d4fd (diff)
downloadansible-e276770ee9efac3a98c3f1116d9cd9c992ca8c9e.tar.gz
Removed repeated introduction paragraph (#78691)
-rw-r--r--docs/docsite/rst/dev_guide/testing.rst10
1 files changed, 0 insertions, 10 deletions
diff --git a/docs/docsite/rst/dev_guide/testing.rst b/docs/docsite/rst/dev_guide/testing.rst
index 31c2153e0d..02a1f27655 100644
--- a/docs/docsite/rst/dev_guide/testing.rst
+++ b/docs/docsite/rst/dev_guide/testing.rst
@@ -41,16 +41,6 @@ At a high level we have the following classifications of tests:
* Tests directly against individual parts of the code base.
-If you're a developer, one of the most valuable things you can do is look at the GitHub
-issues list and help fix bugs. We almost always prioritize bug fixing over feature
-development.
-
-Even for non developers, helping to test pull requests for bug fixes and features is still
-immensely valuable. Ansible users who understand writing playbooks and roles should be
-able to add integration tests and so GitHub pull requests with integration tests that show
-bugs in action will also be a great way to help.
-
-
Testing within GitHub & Azure Pipelines
=======================================