-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[core] Remove dangerfile #1307
[core] Remove dangerfile #1307
Conversation
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I'm not following, what's the advantage? This looks like the DX regressed here. The problems with this approach:
I have preventively removed the Netlify comment, assuming the case is convincing and we will take the step backward. But maybe I'm missing something, and the points I listed aren't less of a pain than the reason behind this change. |
The main advantage for me is having the deployment URL available as a QR code. I'm sure it would be possible to implement it using danger, but this was the simplest way. We currently don't use danger for anything else. Could you please re-enable Netlify comments? When we implement any new features with danger, we can come back to it. |
Ok, restored, and issue created for where we are heading: mui/mui-public#261. |
If we move to Vercel to host the docs, this issue would make sense too, e.g. chakra-ui/chakra-ui#9470 (comment) the QR code is not there. |
Replaced custom danger-based site deployment notifications with the one coming from Netlify for better DX.
Before:
After: