ci: automating the deployment process

[Enase]

Attempt to resolve the "automating the deployment process so at least for the next we will get an auto deploy once merged to master" request from @glicht

Steps required:

• Add email and api tokens here
• Test it

[coveralls]

Pull Request Test Coverage Report for Build 249

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 93.939%

---

Totals
Change from base Build 247:	0.0%
Covered Lines:	130
Relevant Lines:	136

---

💛 - Coveralls

[glicht]

Thanks for contributing this. I've added this functionality based on your PR directly to master.

[Enase]

Hi @glicht

I'm trying to publish a production release by community request according to a guide you made for us but unfortunately I'm not able to create PR from tag to release branch (in my case it's v3.2.0) and I still able create PR from master to release. In some reason (us I understand) I don't have permissions to create PR from tag to master.

Could you look at the permissions or update Publishing a Production Release (Maintainers) section in README.md?

Thanks in advance.

[Enase]

@glicht Hi again.

As I can see, the last release you've merged from master brunch so I consider to create release in the same way from master. So it's not a blocker for us, but it would be better to update README.md.