-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add automation to twitter usage #27
Comments
Having user's email from github handle, can we also get their twitter handle too. @Uran198 thoughts? (might need to check out twitter api). |
@tushar-rishav feel free to assign yourself. IMO it's better asking users for their twitter handlers, as some may not want to be mentioned, or want to be mentioned with another account, etc. |
We have the https://github.com/coala-analyzer/coala/wiki/Community-list Sincerely, Lasse Schuirmann [email protected] On 13 July 2016 at 14:33, Attila [email protected] wrote:
|
Unassigning due to inactivity. |
Right now, all the twitter stuff is managed by @sims1253, so to take some work from his shoulders, there should be a bot that will automate to some extend interaction with twitter.
The goal is that after merged PR, someone from specific (configurable) team can comment something like:
The bot should pick that up, look up author(s) of commits from PR, based on Github username look up Twitter username, look up relevant commits and possibly add the link. From all this information create and post to twitter, mentioning the author. Maybe it'll be also great if it could pick up related hashtags and add them automatically as well.
If you'll have any ideas on how to automate either managing of coala or twitter interaction, or what features this bot may have, feel free to share. Also, if there is already something similar, it would be great to know.
If you're planning to work on this, please ping @sils1297. He may share some code with you for interaction with Github, so you won't have to build this from ground up.
The text was updated successfully, but these errors were encountered: