Skip to content
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.

Sign up for GitHub

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

Jump to bottom

email notifications on release #748

Closed
yegor256 opened this issue Jan 20, 2015 · 13 comments
Closed

email notifications on release #748

yegor256 opened this issue Jan 20, 2015 · 13 comments
Labels
enhancement

Comments

@yegor256
Copy link
Owner

yegor256 commented Jan 20, 2015 •
edited by alex-palevsky
Loading

Let's make it possible to receive email notifications on every release, for example (.rultor.yml):

release:
  email:
    - [email protected]
    - [email protected]

Similar to what we do in CommentsTag we should do here - send an email to all listed addresses. The body of the email should contain similar text to what we create for the tag comment. Let's use jcabi-email for email sending.
@alex-palevsky
Copy link
Contributor

this task will get someone's attention soon

@alex-palevsky
Copy link
Contributor

@alevohin it's your task now

@alex-palevsky
Copy link
Contributor

@yegor256 thank you for the ticket reported, I topped your account for 15 mins, transaction 000-64c09436

@alevohin
Copy link
Contributor

@yegor256 what subject of letter must be?

@yegor256
Copy link
Owner Author

@alevohin how about ${tag} released!

@alevohin
Copy link
Contributor

@yegor256 ok. Maybe something like user/repo ${tag} released!?
I think tag is not enough verbose (it's something like "1.3.4").

@yegor256
Copy link
Owner Author

@alevohin yes, totally agree

alevohin pushed a commit to alevohin/rultor that referenced this issue Jan 20, 2015
Issue yegor256#748 Implemented email notifications on release (only u…
1033fac 
…nit-test)
@alevohin alevohin mentioned this issue Jan 20, 2015
Merged
@alevohin
Copy link
Contributor

@yegor256 PR was merged. Please check and close issue.

@yegor256
Copy link
Owner Author

@alevohin thanks!

@alex-palevsky
Copy link
Contributor

@alevohin I just added 30 mins to your account, many thanks for your contribution... +30 added to your rating, at the moment it is: +345

@alex-palevsky
Copy link
Contributor

3 puzzles were created here: 748-9cbe7474, 748-bb1cb5c5, 748-a3bd319f

@alex-palevsky alex-palevsky mentioned this issue Apr 9, 2015
Closed
@alex-palevsky
Copy link
Contributor

@yegor256 last 3 puzzles 748-9cbe7474/#830, 748-bb1cb5c5/#828, 748-a3bd319f/#829 that originated from here were solved

@0pdd 0pdd mentioned this issue Apr 21, 2017
Open
This was referenced Jul 11, 2022
Open
Open
Open
@0pdd
Copy link
Collaborator

0pdd commented Jul 11, 2022

@yegor256 3 puzzles #1372, #1373, #1377 are still not solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yegor256 @alevohin @alex-palevsky @0pdd