Skip to content

Webhooks: user email property #27918

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
SunnyWolf opened this issue Nov 5, 2023 · 0 comments · Fixed by #33033
Closed

Webhooks: user email property #27918

SunnyWolf opened this issue Nov 5, 2023 · 0 comments · Fixed by #33033
Labels

Comments

@SunnyWolf
Copy link

SunnyWolf commented Nov 5, 2023

Description

I am using gogs webhooks to integrate gitea events to Bitrix24.
I noticed some strange in json POST request.

X-Gogs-Event: pull_request
...
{
  "action": "opened",
  "number": 3,
  "pull_request": {
    ...
    "user": {
      ...
      "email": "[email protected]",
      ...
    },
...
}

All structures with user info contains field email with wrong email. In my case sevice takes NO_REPLY_ADDRESS variable and put it after user name.
In Config Cheats page there is such description:

NO_REPLY_ADDRESS: noreply.DOMAIN Value for the domain part of the user's email address in the Git log if user has set KeepEmailPrivate to true. DOMAIN resolves to the value in server.DOMAIN. The user's email will be replaced with a concatenation of the user name in lower case, "@" and NO_REPLY_ADDRESS.

I checked KeepEmailPrivate property for account and it is disabled.

Also same could be discovered on test server
https://try.gitea.io/user/settings/hooks/1306

Gitea Version

1.20.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Windows

How are you running Gitea?

Windows build

Database

PostgreSQL

wxiaoguang added a commit that referenced this issue Dec 29, 2024
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Mar 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant