Feature: Allow custom webhooks with custom http header + body #5790

New Issue

GiteaMirror · 2025-11-02T06:36:04-06:00

GiteaMirror commented

2025-11-02 06:36:04 -06:00

Originally created by @izelnakri on GitHub (Jul 27, 2020).

Description

Hi there,

I wanted to implement a gitea<->argo CI/CD system, and for this I need to make a HTTP POST request to my argo server with a Bearer token.

In other words in the UI we need a way to add custom http headers and http body(the argo workflow template to trigger via json), not just url and http methods. I think this is an essential feature that gitea needs to support. I can create a simple node.js server that parses the webhooks and makes my requests to the argo server but thats very hacky.

Originally created by @izelnakri on GitHub (Jul 27, 2020). ## Description Hi there, I wanted to implement a gitea<->argo CI/CD system, and for this I need to make a HTTP POST request to my argo server with a Bearer token. In other words in the UI we need a way to add custom http headers and http body(the argo workflow template to trigger via json), not just url and http methods. I think this is an essential feature that gitea needs to support. I can create a simple node.js server that parses the webhooks and makes my requests to the argo server but thats very hacky.

GiteaMirror added the issue/confirmed label 2025-11-02 06:36:04 -06:00

GiteaMirror closed this issue

2025-11-02 06:36:05 -06:00

GiteaMirror commented

2025-11-02 06:36:05 -06:00

@jolheiser commented on GitHub (Jul 27, 2020):

Related or duplicate of #1089?

@jolheiser commented on GitHub (Jul 27, 2020): Related or duplicate of #1089?

GiteaMirror commented

2025-11-02 06:36:05 -06:00

@izelnakri commented on GitHub (Jul 27, 2020):

Yes I had seen/skimmed that issue, the suggestion there seemed more complex and handles more cases. I didn't want to give an impression that I endorse all the suggestions there, although I dont mean I agree or disagree with their approach.

What Im suggesting here is rather adding 2 form sections to Gitea webhooks: http headers and http body(with default prefilled perhaps)

@izelnakri commented on GitHub (Jul 27, 2020): Yes I had seen/skimmed that issue, the suggestion there seemed more complex and handles more cases. I didn't want to give an impression that I endorse all the suggestions there, although I dont mean I agree or disagree with their approach. What Im suggesting here is rather adding 2 form sections to Gitea webhooks: http headers and http body(with default prefilled perhaps)

GiteaMirror commented

2025-11-02 06:36:05 -06:00

@stale[bot] commented on GitHub (Oct 4, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 4, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:36:06 -06:00

@techknowlogick commented on GitHub (Aug 1, 2021):

Merging this into https://github.com/go-gitea/gitea/issues/1089 (and the contents of the template can be covered there, incl. headers)

@techknowlogick commented on GitHub (Aug 1, 2021): Merging this into https://github.com/go-gitea/gitea/issues/1089 (and the contents of the template can be covered there, incl. headers)

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#5790