This repository has been archived by the owner on Aug 31, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
Optionally wait for releases to contain a name / body / attachements #9
Labels
Comments
Hi, it's a good idea, but I don't have time to implement it, you are
welcome to submit a PR :)
Richard
tor. 20. apr. 2017 kl. 08:59 skrev Sebastian Schuberth <
[email protected]>:
… I recently got notified about PMD 5.5.6:
[image: 2017-04-20_085034]
<https://cloud.githubusercontent.com/assets/349154/25217300/9effdce8-25a6-11e7-813c-96e997daec55.png>
As you can see from the screenshot, while a release was created from a
tag, the release does not have a name, body or attachments yet. How about
adding an option to only trigger the notification once a release has some
name / body / attachments?
More generally, some additional options would be nice, like whether to
consider prereleases or not.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFe708f-2uYa25AB5N8xYX7HzxVtndORks5rxwJqgaJpZM4NCnkr>
.
|
Maybe some time, if I feel like doing JavaScript / TypeScript (which is hardly ever the case) :-D |
Hehe, feel free ;) I'll leave this as closed at the moment tho :) |
Why closing it when you agree it's a good idea? IMO it should stay open for contributors to pick, just label it accordingly. |
I agree. @Richard87 Just add the label |
Thanks guys, you are right :) I'm new to this Open Source stuff ;) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I recently got notified about PMD 5.5.6:
As you can see from the screenshot, while a release was created from a tag, the release does not have a name, body or attachments yet. How about adding an option to only trigger the notification once a release has some name / body / attachments?
More generally, some additional options would be nice, like whether to consider prereleases or not.
The text was updated successfully, but these errors were encountered: