You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In unifying some of the patterns for notifications, we noticed that the pseudo-notification for a disconnected webhook stands out. A couple patterns for moving this would be:
An indicator to let users know that project is incorrectly configured
Email notification on the problem, if it persists?
When a webhook is not configured correctly, instead of notifications pointing to the connect services page, we should point users with a persistent notification that points to the integration page. The integration page would mention the underlying issue ("You need to connect a GitHub account") with a pointer to how to resolve the issue.
With this, the notification can be removed from the base project base template.
The text was updated successfully, but these errors were encountered:
In unifying some of the patterns for notifications, we noticed that the pseudo-notification for a disconnected webhook stands out. A couple patterns for moving this would be:
With this, the notification can be removed from the base project base template.
The text was updated successfully, but these errors were encountered: