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

[Feature Request] Webhooks message customization #4919

New Issue
Closed
opened 2025-11-02 06:07:18 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 06:07:18 -06:00
Owner
Copy Link

Originally created by @davydov-vyacheslav on GitHub (Feb 22, 2020).

I'd like Gitea has customized messages for Webhooks.

As for now, Gitea Webhooks messages are hardcoded and there is no way for customization.

I think that following things make Gitea Webhooks functionality much better:

  • on webhooks page (maybe even better in config file) add Custom message field where user is able to set own message for specific action
  • user should be allowed to have/use predefined "variables", like %repo% for link to org/repository with the name,%issue.title% - issue's title if the action type in scope of issue and so on.

And as result, I'd like to be able to set (e.g. for pull request) message like: %user% has submitted pull-request to %repo%.

Originally created by @davydov-vyacheslav on GitHub (Feb 22, 2020). I'd like Gitea has customized messages for Webhooks. As for now, Gitea Webhooks messages are hardcoded and there is no way for customization. I think that following things make Gitea Webhooks functionality much better: - on webhooks page (maybe even better in config file) add `Custom message` field where user is able to set own message for specific action - user should be allowed to have/use predefined "variables", like `%repo%` for link to org/repository with the name,%issue.title% - issue's title if the action type in scope of issue and so on. And as result, I'd like to be able to set (e.g. for pull request) message like: %user% has submitted pull-request to %repo%.
GiteaMirror added the issue/duplicate label 2025-11-02 06:07:18 -06:00
GiteaMirror commented 2025-11-02 06:07:19 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Feb 22, 2020):

This would be covered by #1089

@jolheiser commented on GitHub (Feb 22, 2020): This would be covered by #1089
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 issue/duplicate
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#4919
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?