Setting releases to create packages in pypi.org so we can productioni… (

#6)

* Setting releases to create packages in pypi.org so we can productionise the code. Adding badges of different integrations.

.github/workflows/release.yml

@@ -38,9 +38,9 @@ jobs:
       run: pip install setuptools wheel twine
     - name: Build and publish
       env:
-        TWINE_REPOSITORY_URL: https://test.pypi.org/legacy/
+        TWINE_REPOSITORY_URL: https://upload.pypi.org/legacy/
         TWINE_USERNAME: __token__
-        TWINE_PASSWORD: ${{ secrets.TESTPYPI_TOKEN }}
+        TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
       run: |
         python setup.py clean sdist bdist_wheel
         twine upload dist/*

README.md

@@ -1,7 +1,19 @@
 # iab-tcf
 
+[![Build Status](https://travis-ci.org/gguridi/iab-tcf.svg?branch=master)](https://travis-ci.org/gguridi/iab-tcf)
+[![codecov](https://codecov.io/gh/gguridi/iab-tcf/branch/master/graph/badge.svg)](https://codecov.io/gh/gguridi/iab-tcf)
+![Releasing](https://github.com/gguridi/iab-tcf/workflows/Releasing/badge.svg)
+
 A Python implementation of the IAB consent strings (v1.1 and v2)
 
+# Installing
+
+Install and update using pip:
+
+```bash
+pip install -U iab-tcf
+```
+
 # A Simple Example
 
 In order to decode a v1.1 or v2 consent string automatically we can do: