github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[Telegram] Webhook "Active" flag ignored #8754

New Issue
Closed
opened 2025-11-02 08:16:31 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 08:16:31 -06:00
Owner
Copy Link

Originally created by @bryanpedini on GitHub (Mar 26, 2022).

Description

I noticed that after configuring a Telegram webhook, new repos in a private org trigger the webhook too, even private repos themselves (but this is a separate issue).

I then disabled the webhook by unflagging the "Active" section in the webhook settings, tho it still sends out Telegram messages via the bot.

In the logs I flag the webhook enabled, save the webhook configuration, disable it again and save it again, create a test repository, and finally delete it.

Gitea Version

1.16.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/bryanpedini/3f191cf3b8ae706541f511e809961282

Screenshots

N/A

Git Version

2.20.1

Operating System

Debian 10 + official Docker image

How are you running Gitea?

Docker Compose stack: deployments/gitea

Database

MySQL

Originally created by @bryanpedini on GitHub (Mar 26, 2022). ### Description I noticed that after configuring a Telegram webhook, new repos in a private org trigger the webhook too, even private repos themselves (but this is a separate issue). I then disabled the webhook by unflagging the "Active" section in the webhook settings, tho it still sends out Telegram messages via the bot. In the logs I flag the webhook enabled, save the webhook configuration, disable it again and save it again, create a test repository, and finally delete it. ### Gitea Version 1.16.5 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist https://gist.github.com/bryanpedini/3f191cf3b8ae706541f511e809961282 ### Screenshots N/A ### Git Version 2.20.1 ### Operating System Debian 10 + official Docker image ### How are you running Gitea? Docker Compose stack: [deployments/gitea](https://git.bjphoster.com/deployments/gitea.git) ### Database MySQL
GiteaMirror added the type/bug label 2025-11-02 08:16:31 -06:00
GiteaMirror commented 2025-11-02 08:16:32 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Mar 27, 2022):

Is this a system webhook or a repository webhook?

@zeripath commented on GitHub (Mar 27, 2022): Is this a system webhook or a repository webhook?
GiteaMirror commented 2025-11-02 08:16:32 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Mar 27, 2022):

I've noticed a few bugs - which assuming that these represent your problems then should they should fix the problem.

@zeripath commented on GitHub (Mar 27, 2022): I've noticed a few bugs - which assuming that these represent your problems then should they should fix the problem.
GiteaMirror commented 2025-11-02 08:16:32 -06:00
Author
Owner
Copy Link

@bryanpedini commented on GitHub (Mar 27, 2022):

I've noticed a few bugs - which assuming that these represent your problems then should they should fix the problem.

Thank you a lot Zeripath!!

Is this a system webhook or a repository webhook?

Sorry for the missing information, it was a system-wide wehbook that sent a Telegram notification whenever action X happened on the Gitea server.

Would it be possible to take a look at why it sends webooks even for private repos too? Or is it "normal" behavior?

@bryanpedini commented on GitHub (Mar 27, 2022): > I've noticed a few bugs - which assuming that these represent your problems then should they should fix the problem. Thank you a lot Zeripath!! > Is this a system webhook or a repository webhook? Sorry for the missing information, it was a system-wide wehbook that sent a Telegram notification whenever action X happened on the Gitea server. Would it be possible to take a look at why it sends webooks even for private repos too? Or is it "normal" behavior?
GiteaMirror commented 2025-11-02 08:16:33 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Mar 27, 2022):

A system webhook runs on every webhook - that is why it is a system webhook.

@zeripath commented on GitHub (Mar 27, 2022): A system webhook runs on every webhook - that is why it is a system webhook.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8754
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?