Ask HN: Good company culture to send commit notifications to Slack/Discord?

[schmidt87]

I run a small team of developers. I like having a dedicated Slack/Discord channel called e.g. "commits"", with a webhook to git, which notifies about commits/pushes (only to main branch).

I find that it helpful, knowing what other developers are working on. But I assume that others might find it invasive and too public.

I am wondering what others think about this.

[mytailorisrich]

People should know what others are working on through discussions, status updates, team meetings, project plan, Jira/whatever, etc. They should not find out when a commit occurs.

There would also be code reviews (right?) so at least a subset of most relevant people should know what is happening before the commit occurs (after code review).

It's also a good idea to have something like gitweb available so anyone can quickly have a look at what has happened on the master repo.

To me pushed notifications seem like noise.

[jalapenos]

The main problem I see is that it's one more channel everyone will need to mute.

If the goal is just you watching their work then maybe it could send it to a private channel only you're in.