Gitea not sending email to 'watcher' on a commit/push #2124

Closed
opened 2025-11-02 04:24:46 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @mgoddard27 on GitHub (Jul 31, 2018).

  • Gitea version (or commit ref): Gitea Version: 1.5.0+rc1-73-gd0fef4395
  • Git version: 1.8
  • Operating system: CentOS7
  • Database (use [x]):
    • PostgreSQL
    • [x ] MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • [x ] No ( that site is currently down )
    • Not relevant
  • Log gist:

Description

A push up to the repo does not send an email to the watcher.

Screenshots

Originally created by @mgoddard27 on GitHub (Jul 31, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): Gitea Version: 1.5.0+rc1-73-gd0fef4395 - Git version: 1.8 - Operating system: CentOS7 - Database (use `[x]`): - [ ] PostgreSQL - [x ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x ] No ( that site is currently down ) - [ ] Not relevant - Log gist: ## Description A push up to the repo does not send an email to the watcher. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/enhancementissue/stale labels 2025-11-02 04:24:47 -06:00
Author
Owner

@adjurk commented on GitHub (Aug 3, 2018):

Can confirm on Gitea Version 1.4.2

@adjurk commented on GitHub (Aug 3, 2018): Can confirm on Gitea Version 1.4.2
Author
Owner

@stale[bot] commented on GitHub (Jan 15, 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 (Jan 15, 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.
Author
Owner

@stale[bot] commented on GitHub (Feb 19, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 19, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2124