Skip to content

No notification when issue is closed via git commit #1464

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

Closed
2 of 7 tasks
RichieB2B opened this issue Apr 7, 2017 · 7 comments
Closed
2 of 7 tasks

No notification when issue is closed via git commit #1464

RichieB2B opened this issue Apr 7, 2017 · 7 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@RichieB2B
Copy link
Contributor

  • Gitea version (or commit ref): 1.1.0
  • Git version: 1.9.4
  • Operating system: CentOS 6
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When an issue is closed using a git commit ("fixes #n") no notification E-mail is sent.

@lunny lunny added the type/bug label Apr 7, 2017
@lunny lunny added this to the 1.2.0 milestone Apr 7, 2017
@lunny
Copy link
Member

lunny commented Apr 7, 2017

@andreynering I confirm this is a bug. maybe you can help to find the reason.

@andreynering
Copy link
Contributor

@lunny I think it's not a bug, just wasn't implemented yet.

Maybe we should integrate web and email notifications first.

@lunny lunny added type/feature Completely new functionality. Can only be merged if feature freeze is not active. and removed type/bug labels Apr 7, 2017
@lunny lunny modified the milestones: 1.x.x, 1.2.0 Apr 7, 2017
@ghost
Copy link

ghost commented Aug 2, 2018

Just to add that follow-up comments on closed issues, when still subscribed, is also failing to deliver email notifications (web notifications work), tested on Gitea 1.4.3.
Just saying that maybe it doesn't have to be a git commit, the issue just needs to be closed.

@stale
Copy link

stale bot commented Jan 16, 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 stale bot added the issue/stale label Jan 16, 2019
@RichieB2B
Copy link
Contributor Author

Thanks stalebot for reminding us this issue has not been addressed in 2 years.

@stale stale bot removed the issue/stale label Jan 16, 2019
@zeripath
Copy link
Contributor

@RichieB2B Are you still experiencing this bug on latest?

@RichieB2B
Copy link
Contributor Author

Nope, I can't reproduce this issue in gitea 1.6.4, thanks!

@lunny lunny removed this from the 1.x.x milestone Jan 16, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

4 participants