-
Notifications
You must be signed in to change notification settings - Fork 6
Explore connecting GitHub and Slack #75
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
Comments
There are many issues, and as such probably something that I'll do if it happens at all. Which is fine! |
We can always share particular messages from the website channel, which is connected to GitHub (though this needs to be redone every year), to the larger con channel. Were there specific messages you thought were relevant? Like when we address an issue someone raised ("there are no locations for X")? That might best be done ad hoc by group members sharing particular messages, as opposed to setting up a noisy integration. We can configure the GitHub integration to only share certain kinds of notifications: issues, PRs, commits, releases, deployments. But all of those seem too noisy or inconsistent to me, e.g. we do not create issues or PRs for many changes especially during the con when we're busy, and every commit or deployment is obviously too much. |
I'm thinking pretty narrowly here. Somewhat like the case you mention, either responding to a community comment about website content or website maintainers making a material change. It would go something like this: con channel: "Where will the breakout sessions be?" (I think this might have been roughly the proximate case that led me to create this issue) The ⭐️ is new and the ??? is the part that's uncertain or unknown. How do GitHub actions get triggered by this code activity and not that code activity. |
I can see some ways that certain kinds of changes to the conference website, under certain circumstances, could be helpful to the conference by pushing the change info to the code4libcon channel.
The text was updated successfully, but these errors were encountered: