KIT-3282 added note on testing to readme

.vscode/settings.json

@@ -22,10 +22,18 @@
     "python.linting.enabled": true,
     "python.linting.flake8Enabled": true,
     "python.formatting.provider": "black",
-    "python.formatting.blackArgs": [ "--line-length=120" ],
-    "[python]": { "editor.formatOnSave": true },
-    "[json]": { "editor.formatOnSave": true},
-    "editor.codeActionsOnSave": { "source.organizeImports": true },
+    "python.formatting.blackArgs": [
+        "--line-length=120"
+    ],
+    "[python]": {
+        "editor.formatOnSave": true
+    },
+    "[json]": {
+        "editor.formatOnSave": true
+    },
+    "editor.codeActionsOnSave": {
+        "source.organizeImports": "explicit"
+    },
     "python.linting.mypyEnabled": true,
     "mypy.targets": [
         // Required by dmypy - otherwise mypy has an error in vscode

README.md

@@ -172,3 +172,11 @@ Just install vscode with dev containers extension. All required extensions and c
 * Update the version in setup.py and commit your change
 * Create a tag with the same version number
 * Let github do the rest
+
+## How to test
+
+To avoid publishing to pypi unnecessarily you can do as follows
+
+* Tag your branch however you like
+* Use the chosen tag in the requirements.txt-file of the project you want to test this library in, eg. `sag_py_logging==<your tag>`
+* Rebuild/redeploy your project