-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Create a bridge between submission PRs and Slack #1630
Comments
Willing to take this on, could be automated with a github action that checks the pr for the |
Wouldn't this be as simple as an airtable automation? |
What exactly is the scope of games here? Will we use this to announce the accepted games or act like a way for the community to interact and review games |
The latter. Any new submission should get a post. Looking down the line comments on threads of the submission should also be posted. And github comments posted in the thread. |
@leomcelroy can you please describe exactly the copy you want here, and exactly what situations you want to trigger the messages? An example or two would be good to ensure we implement it exactly how you want it. For new submissions I assume it'll be something like "A new sprig game was submitted! Check it out!" or something, with some link or whatever... but if you could be specific so we don't have to assume anything, that would be ideal. |
When someone PRs a new game submission the bot should post to the Slack.
|
Seems good, I already have a message done to be submitted in that case. |
@grymmy Do we want to use a slack bot with this? That would require integration with a backend, I don't recall if we have one. I |
Slack bot seems fine if what we desire is auto-post slack msg in #sprig with above copy only on first PR open... |
Whenever someone submits a game a bot should post the submission text and a link to PR in the #sprig channel on Slack.
An even better version of this would also post a playable link to the game.
The objective would be to encourage community members to participate in review and giving feedback.
This could also be extended by automatically posting thread responses on the PR.
The text was updated successfully, but these errors were encountered: