Gitter interaction
Open
@bdunne is already working on this.
Since Feb 2, 2017.
enhancement
new worker
pinned
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
I did a short spike on this locally trying to use Gitter's IRC bridge and the cinch gem and it was really simple to get started. However, I ran into this issue (https://github.com/gitterHQ/irc-bridge/pull/54), and until that's in, I couldn't get the bot to actually reply. So, this is a placeholder for myself once I get back to it.
Launching it is as simple as putting it in the Procfile.
#!/usr/bin/env ruby
require 'cinch'
bot = Cinch::Bot.new do
configure do |c|
c.server = "irc.gitter.im"
c.ssl.use = true
c.nick = "miq-bot"
c.password = '' #REDACTED
c.channels = [
"#manageiq/manageiq",
"#manageiq/miq_bot"
]
end
on :message, "hello" do |m|
m.reply "Hello, #{m.user.nick}"
end
end
bot.start
Once we have IRC interaction, some possible follow up RFEs would be
- Allowing some of the commands we use in the GithubNotificationMonitor to be reused in Gitter (requires separation of GithubNotificationMonitor's reaction/reply half)
- New commands for chat only
@miq-bot statuscould be queue statistics or something@miq-bot gif <keywords>and it will search @chrisarcand's gif list ;) 😜
- Watching
#manageiqon IRC, then pinging the Gitter channel that there is activity over there - Watching
#manageiqon IRC, then pinging IRC that chat no longer occurs there and instructions to go to Gitter if they choose
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.