-
Notifications
You must be signed in to change notification settings - Fork 190
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
[Feature] PR Slack notifier #83
Comments
I thought we might be able to have the Tinker Bot accomplish this - do we need to write our own tool or can we use that? |
Just updated my initial comment with more detail @AetherUnbound 😄 |
I wish there was a way to do a condensed preview using the default integration, but alas it seems like it's been an open issue for a while 😞 |
I see it as an opportunity to play with Rust 😁 If you want to modify that existing script to support multiple accounts/repos/channels, I'll host it and run it on the same instance I'm running ours. I can help with any tweaks too, but also totally understand it's a simple easy script that rewriting in Python would be pretty quick. |
Well that sounds easy 😄 let's go for it! |
No Rust. 😢 |
🦀 😢 |
Reject modernity. Return to shell. 😂 |
…llib3-1.26.5 Bump urllib3 from 1.26.4 to 1.26.5 in /openverse-api
Problem
We would like a way to see new Pull Requests in our PR slack channel. We don't want this integration to generate too much noise, these notifications are intended to be a quick, casual ping "hey, check out this new PR if you want!". The native GitHub Slack integration is not a good fit, it produces a "wall of text" response for each PR, with too much clutter.
Description
We could write a script in JS or Python in this repository, similar to @mkaz's work on
TinkerNotifier
, the bot for the tinker team (https://github.com/mkaz/octoack), that simply posts all newopenverse-*
repo pull requests to our slack channel, with a link.We could use that bot, my initial thoughts for not using it are:
The text was updated successfully, but these errors were encountered: