Mail notification on commit #4052

@bobemoe commented on GitHub (Oct 3, 2019):

I don't think this is implemented yet. There is discussion (and possibly a fork with this) along with other notification improvements over at https://github.com/go-gitea/gitea/issues/145

@bobemoe commented on GitHub (Oct 3, 2019): I don't _think_ this is implemented yet. There is discussion (and possibly a fork with this) along with other notification improvements over at https://github.com/go-gitea/gitea/issues/145

GiteaMirror commented

@lunny commented on GitHub (Oct 4, 2019):

We needs a PR to implement that.

@lunny commented on GitHub (Oct 4, 2019): We needs a PR to implement that.

GiteaMirror commented

@stale[bot] commented on GitHub (Dec 3, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 3, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

@lunny commented on GitHub (Dec 3, 2019):

I remember one of @guillep2k 's PR will fix this.

@lunny commented on GitHub (Dec 3, 2019): I remember one of @guillep2k 's PR will fix this.

GiteaMirror commented

@guillep2k commented on GitHub (Dec 3, 2019):

@lunny Sorry, my PRs were about updating references from commit messages, but commits do not send mail notifications per-se. CommitRepoAction() should handle this, and it creates an action through models.NotifyWatchers, but mails are not generated AFAIK.

@guillep2k commented on GitHub (Dec 3, 2019): @lunny Sorry, my PRs were about updating references from commit messages, but commits do not send mail notifications per-se. `CommitRepoAction()` should handle this, and it creates an `action` through `models.NotifyWatchers`, but mails are not generated AFAIK.

GiteaMirror commented

@lunny commented on GitHub (Dec 3, 2019):

Implement NotifyPushCommits will resolve the issue?

@lunny commented on GitHub (Dec 3, 2019): Implement `NotifyPushCommits` will resolve the issue?

GiteaMirror commented

@guillep2k commented on GitHub (Dec 3, 2019):

It looks like most of CommitRepoAction should be moved to notifications. But for a minimal implementation yes, NotifyPushCommits would be enough.

@guillep2k commented on GitHub (Dec 3, 2019): It looks like most of `CommitRepoAction` should be moved to notifications. But for a minimal implementation yes, `NotifyPushCommits` would be enough.

GiteaMirror commented

@stale[bot] commented on GitHub (Feb 1, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 1, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

@guillep2k commented on GitHub (Feb 1, 2020):

Bump!

@guillep2k commented on GitHub (Feb 1, 2020): Bump!

GiteaMirror commented

@bendem commented on GitHub (Jul 7, 2020):

On top of that, a visual indicator in the PR's conversation about new commit would also help.

See github including commits in the conversation:

@bendem commented on GitHub (Jul 7, 2020): On top of that, a visual indicator in the PR's conversation about new commit would also help. See github including commits in the conversation: ![image](https://user-images.githubusercontent.com/2681677/86755021-9bf2a880-c041-11ea-9775-0b5924d52c06.png)

GiteaMirror commented

@alam-R commented on GitHub (Mar 11, 2021):

As a workaround for mailing pushing events, I have created a minimal Java Service to handle a push webhook and map it to mail.
It needs a lot of customization but it can be a workaround for small projects.
For anyone who is interested: https://github.com/alam-R/giteaWebhookMailProxy

Cheers!

@alam-R commented on GitHub (Mar 11, 2021): As a workaround for mailing pushing events, I have created a minimal Java Service to handle a push webhook and map it to mail. It needs a lot of customization but it can be a workaround for small projects. For anyone who is interested: https://github.com/alam-R/giteaWebhookMailProxy Cheers!

GiteaMirror commented

@Zyzto commented on GitHub (Jul 5, 2021):

any news on this ?

@Zyzto commented on GitHub (Jul 5, 2021): any news on this ?

GiteaMirror commented