Can we put those automated bleeding edge notifications in a separate channel? The project-specific channel would make more sense than the global #company channel.
@jaswsinc writes...
Agree. I think the official release announcements should be in a project-specific channel also. This will need to be updated in the build system by one of us.
Reopening this issue. The Slack channel needs to be configurable, for two reasons.
Slack has a limit on the number of characters allowed in a channel. If the project slug exceeds that limit, we will be forced to get creative with the Slack channel name, and therefore the automatic mapping will be thrown off in that case; e.g., woocommerce-kb-articles is too long.
Some projects may prefer to ride on a parent project channel for notifications. Or, they might prefer to use a shorter channel name for easier Slack navigation; e.g., wc-intercom instead of woocommerce-intercom.
@raamdev writes...
@jaswsinc writes...