-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Too fast emails? #32
Comments
so this is what Sibbell calls realtime, interesting i can add a checkbox to let you control if you wanna wait for release description or you want email ASAP. i probably cannot determine automatically if release description will follow, because some repos simply don't have release descriptions at all, e.g. https://github.com/angular/angular/releases |
Yes, I know.
Good thought. I think, there can be delay for 30 minutes or even 2 hours. Maybe some delay by default. Real-time is cool, but I'm not sure that this is better than email this release description. |
some people do want the emails ASAP tho, e.g. #13 |
They can enable real-time, I'm talking just about default. But as you wish. |
+1 from me on this one, having a setting for it to wait for the description would be very useful 👍 |
This means you can check this. So if a repository doesn't have at least one release with a release description, then you can send the email instantly even if this option is enabled. If it does have at least one release with a release description then you can probably use a delay as previously mentioned if this option is enabled. Also extracting details form the repository's |
This is my dream for service like GitPunch, but I think it's very difficult (too many formats, too many regexps). |
A simple way would be to just have an option to delay the emails by a set amount or something... |
Hello!
Some releases emailed too fast, I think, and emails have no release description.
Examples:
Babel
3:21 AM
11:09 AM
Autoprefixer (May 13)
11:20 AM
4:12 PM
The text was updated successfully, but these errors were encountered: