Only disable GitHub comments on main branch

[IGassmann]

github.silent allows us to stop the Vercel bot from commenting on pull requests and commits. However, it doesn't let you decide only to disable comments on the main branch.

Since GitHub already has commit status checks with a link to the deployment, comments on the main are superfluous. They just spam the repository contributors' GitHub inbox every time there's a commit.

That being said, comments on PR are still useful because they provide an easy access link to the deployment to be used for review and also information about Deployment Comments.

That's why it would be great to allow us only to disable those comments on the commits of the main branch.

[amyegan]

Are you suggesting something like git.deploymentEnabled, but for comments instead of deployments?

[IGassmann]

That's right :)

[amyegan]

Thanks for sharing this idea. I sent it to the team 🙂

[tomislavhrenmp]

Any progress on this one? It would be great if we could disable it.

[jonworek]

I came across this discussion when searching for how to disable the vercel bot comments on the PR. It looks like this functionality is now built into the project settings UI, and is deprecated from vercel.json.

See: https://vercel.com/docs/deployments/git/vercel-for-github#silence-github-comments

I have two options visible to me:

"Pull Request Comments" was the setting I was looking to disable.

"Commit Comments" looks like it might be what you're looking for @IGassmann .

[IGassmann]

Unfortunately, as @samthomson mentioned, this configuration doesn't seem to work.

[samthomson]

Why do I still get a commit comment for every push to master?

[samthomson]

@amyegan can you confirm if this is the intended behaviour - that I can't disable vercel bot comments on commits this way, as it seems from the toggle/options that it ought to be disable-able. Or how can I resolve this (aside from disabling all github notifications - which is not something I'm prepared to do).

[amyegan]

@samthomson @IGassmann That is not expected behavior. Thanks for reporting it.

In the interest of gathering info to aid investigation, I have a couple of questions:

• Does the project happen to be part of a monorepo?
• What is the name or a deployment link of the project?

[samthomson]

Sure.

• The project is not part of a mono repo. There is one github repo, but there are two vercel projects that get build from it (each governed by different env vars).
• the repo has two projects attached: 1. guidedtrekking 2. guided-peaks
• Interestingly, building the first project doesn't result in the vercel bot commenting to the repo - only with the second project. From what I can see both vercel projects have the same settings.