FWIW I'm often not really reading this channel because of all the github noise. If it's useful to some people, by all means keep it, as I'm currently not really involved in openlane myself.

@Pepijn de Vos: Unfortunately we were trying to only post notifications from the

staging

and

master

branches, but this isn't supported (https://github.com/integrations/slack/issues/441), so we ended up allowing notifications from all branches... People (e.g., @Riking28) didn't want to be surprised with ~200 commits every now and then preferred to see them coming up gradually. We definitely don't like the noise either, but if you have suggestions, let us know..

Thank you for clarifying.

Could you put them into a different channel?

I'm fine with turning them off if this turned out to be too much! :) I am prepared to be wrong!

@Matt Liberty: That is probably a good idea. Maybe we should do that (+ @Amr Gouhar).

@Ahmed Ghazy, @Matt Liberty: I definitely think this is a good idea, unless someone complains about having two openlane channels.

I think even if someone wants to follow both they would appreciate not having them intermixed

@Matt Liberty: Yes, I agree. @Ahmed Ghazy: Is there a moderator for the workspace that we should ask or should we go ahead and create it right away?

@Ahmed Ghazy @Amr Gouhar any progress on this?

@Matt Liberty: Yes, I posted that on the channel a week ago, #openlane-development is now dedicated to tracking all openlane branches. Here (#openlane), we now only track master, PRs, and issues.

thanks