-
Notifications
You must be signed in to change notification settings - Fork 15
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
Request info bot with GitHub actions #7
Comments
hmmmm - I am a little bit worried that it seems the |
I think we have three more options that could be worth exploring:
Not sure which option is best, but I believe it would be really nice to have the welcome bot in JH. |
+1 to welcome bot 👍 maybe that's a good compromise, since the kind of person we'd probably request more info from is a new user |
Here's the welcome bot in action on The Turing Way: the-turing-way/the-turing-way#1183 (comment) The only downside to this I think was mentioned by @betatim. It will welcome them the first time on all repos. So we may have seasoned KubeSpawner contributors who wander over to z2jh and are welcomed as if they're new. Though it seems to be the path of least resistance so far. |
As long as the message isn't too annoying, I think it could be OK :-) |
My first reaction to the "more info please" bot was that it would fail a lot of the time. Thinking about this a bit to figure out why that was my initial reaction:
So overall it feels like there would be too many cases where the bot is wrong or unhelpful. What do you think of making a canned message that we share in the team and then use the neural network in our contributors to (tweak and) apply it? |
I have played with GitHub actions following this Twitter thread (thanks @choldgraf for pinging me), hoping to achieve what the request-info bot does.
I managed to transpose the bot's behavior into a workflow and you can play with it here.
I got carried away and forgot to check before if GitHub workflows are supported at an org level and found out that they are not 😕
So, unfortunately until behaviorbot/request-info#49 gets merged (and hopefully solves the issue) or workflows are supported organization-wide I don't think we can have a request info bot (as long as we don't copy and paste configs across the repos individually 🤯 )
The text was updated successfully, but these errors were encountered: