Conversation
|
Contributor
📚 Storybook Preview Deployed✅ Preview URL: https://click-o3hpuq45z-clickhouse.vercel.app Built from commit: |
Firefds
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
Currently, visibility on new Pull Requests is inconsistent, leading to delayed feedback loops and missed opportunities for early collaboration. To address this, I’m introducing a new GitHub Action that automates Slack notifications. For example, we've experienced PR that takes longer than >= 3 weeks for any comments or feedback.
This change puts the control back into the developers' hands. You can choose how you want to stay informed, e.g., by joining a tag group or monitoring activity in the channel at your own pace.
Basically, the automation is to reduce or eliminate "missed PRs" and the need for manual follow-ups. Whether they subscribe or not, the consumers/users take responsibility for their level of involvement in the review process.
How?
Contribution checklist?
buildcommand runs locallySecurity checklist?
dangerouslySetInnerHTMLPreview?
N/A