-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Suggestion) Github to Twitter integration #4
Comments
Also I could do the obvious thing and make some easy script that will be checking our repo via Github API and then if new release is found, save the commit number of that last release and tweet it. Then if new release with different commit number is found, it will tweet it again. The problem with this is.. Where to host this. I have my server, but some hosted solution would be always better. |
I may have an azure account to run this kind of stuff... |
I'm reading this now(Sorry for late reaction) I think this would be a nice feauture to have! |
Ok, so another solution. :D Microsoft Azure Functions. But when I get this resolved. With release traffic that we have it will be free for us. (Free is like 4GB of data and 1M events. So.... One release event have like 1kB max? One release per week? => Free) |
Ok so I finished it. Sent @ST-Apps tutorial how to do it and we should be good to go! |
Regarding ST-Apps/PoGo-UWP#886
I also thought about posting on twitter on every new release day before that issue ^^
There is one solution that I found. It's https://zapier.com you can basically create zap, that checks the repo every 15 minutes and if it finds something new it can create tweet. The problem is for now, that it can only act on certain things and New Release is not in it. But we could create new branch on every release and that could be checked for zap. Idk if this is too much cumbersome.. I already posted to their support, if they will support New Release as a trigger.
I will search a little more if there is something else.
Edit: So I got reponse from support, they say that it is the most requested feature for github triggers, but they have no ETA.
The text was updated successfully, but these errors were encountered: