Better Github Integration (non-duplicated deployment messages)
c
chahn
Currently every single time render attempts to deploy something, a new status is dropped on a PR.
As a result our PR threads become MASSIVE and very difficult to follow.
Vercel used to do this too, but has since moved to un update-able comment that updates with the status of the latest deploy.
It would be fantastic if render took a similar approach as a kindness to engineers and PR reviewers everywhere.
See attached screenshots for difference between Vercel and Render.
Log In
O
Olivier Tassinari
OMG yes, this needs to be fixed, it's such a shitshow, see image!
What I would expect is what, e.g. Netlify is doing, they use GitHub checks:
- No cluter, it's very clear what's in progress, what failed, etc.
- You can enforce what
C
Can Duruk
We are running into this noisy PR page issue quite a bit more now that we're adopting monorepos (thank you!) — and it'll only get worse.
Strongly in favor of either a better integration with Github's Deployment / Actions API so that we can see the status directly on the PR page or at least the ability to silence some of the Render messages.
A
Alex Zlotnik
This may be related to https://feedback.render.com/features/p/quiet-preview-environment-mr-comments (if they're using a similar integration framework).