Create issue via email #2995

New Issue

GiteaMirror · 2025-11-02T04:56:34-06:00

GiteaMirror commented

2025-11-02 04:56:34 -06:00

Originally created by @MartinDelille on GitHub (Mar 2, 2019).

Another Gitlab EE feature that would be nice to have in Gitea: https://docs.gitlab.com/ee/administration/incoming_email.html

This feature is blocking the service desk feature: #6219

Originally created by @MartinDelille on GitHub (Mar 2, 2019). Another Gitlab EE feature that would be nice to have in Gitea: https://docs.gitlab.com/ee/administration/incoming_email.html This feature is blocking the service desk feature: #6219

GiteaMirror added the type/feature type/proposal labels 2025-11-02 04:56:34 -06:00

GiteaMirror commented

2025-11-02 04:56:35 -06:00

@MOZGIII commented on GitHub (Mar 5, 2019):

I'd deploy is as a separate unit, and just create a support for creaing issues via API. Rationale is there can be a lot of sources to create an issue, and coupling the gitea with email recieving functionality seems unnesessarily specific. Consuming emails is a tricky thing, and it worth being a separate unit - maybe there is something we could utilize already.
Altough, I'm new here and I don't know how things are done.

@MOZGIII commented on GitHub (Mar 5, 2019): I'd deploy is as a separate unit, and just create a support for creaing issues via API. Rationale is there can be a lot of sources to create an issue, and coupling the gitea with email recieving functionality seems unnesessarily specific. Consuming emails is a tricky thing, and it worth being a separate unit - maybe there is something we could utilize already. Altough, I'm new here and I don't know how things are done.

GiteaMirror commented

2025-11-02 04:56:35 -06:00

@sclu1034 commented on GitHub (Aug 5, 2024):

As can be seen in the timeline, Gitea does now handle incoming emails. Though currently with the restriction "existing users replying to existing issues".

But it does mean it's now a much smaller step towards also accepting messages from addresses that don't belong to a registered user, and to have a repository-wide address that creates new issues/pull requests when messaged.

Running a single-user instance where I would like to be able to accept contributions without having to deal with registered users, I would love to see this.

@sclu1034 commented on GitHub (Aug 5, 2024): As can be seen in the timeline, Gitea does now handle incoming emails. Though currently with the restriction "existing users replying to existing issues". But it does mean it's now a much smaller step towards also accepting messages from addresses that don't belong to a registered user, and to have a repository-wide address that creates new issues/pull requests when messaged. Running a single-user instance where I would like to be able to accept contributions without having to deal with registered users, I would love to see this.

GiteaMirror referenced this issue

2025-11-02 12:16:47 -06:00

[PR #2995] [MERGED] Don't print SQL in unit tests #16704

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2995