Support Pull Request Review Code Comment Webhooks #11291

New Issue

GiteaMirror · 2025-11-02T09:33:32-06:00

GiteaMirror commented

2025-11-02 09:33:32 -06:00

Originally created by @Makonike on GitHub (Jul 20, 2023).

Feature Description

It appears that Gitea has not implemented a webhook for code comments in Pull Requests, similar to what Github offers. I hope to see this feature supported in Gitea, akin to Github's functionality. However, I noticed that the headers containing the event information in Gitea and Github webhooks seem to differ. In Github, the event for code comments on reviews is labeled as "pull_request_review_comment," whereas in Gitea, it seems to be labeled as "pull_request_review_comment" when a review is submitted. If Gitea is not compatible with Github's event, what should be the appropriate event for code comments in Gitea?

I have noticed that Gitea's webhook request headers support both Github and Gogs, but currently, they seem to be different. Upon inspecting the code, I found that the assignments for these headers are the same. Is there any plan to implement a unified approach for these headers in the future?

Screenshots

Two code review comments have been added. Only one webhook was triggered.

Upon inspecting the code, I found that the assignments for these headers are the same.

Originally created by @Makonike on GitHub (Jul 20, 2023). ### Feature Description It appears that Gitea has not implemented a webhook for code comments in Pull Requests, similar to what Github offers. I hope to see this feature supported in Gitea, akin to Github's functionality. However, I noticed that the headers containing the event information in Gitea and Github webhooks seem to differ. In Github, the event for code comments on reviews is labeled as "pull_request_review_comment," whereas in Gitea, it seems to be labeled as "pull_request_review_comment" when a review is submitted. If Gitea is not compatible with Github's event, what should be the appropriate event for code comments in Gitea? I have noticed that Gitea's webhook request headers support both Github and Gogs, but currently, they seem to be different. Upon inspecting the code, I found that the assignments for these headers are the same. Is there any plan to implement a unified approach for these headers in the future? ### Screenshots Two code review comments have been added. Only one webhook was triggered. <img width="353" alt="image" src="https://github.com/go-gitea/gitea/assets/75628309/0fd97afd-54b6-4905-a089-540095c9ec24"> <img width="1124" alt="image" src="https://github.com/go-gitea/gitea/assets/75628309/58574ccc-23b5-4431-a618-d42fe92576e5"> <img width="678" alt="image" src="https://github.com/go-gitea/gitea/assets/75628309/c04d64cb-dd84-4340-aff2-7056dddf98cd"> <img width="620" alt="image" src="https://github.com/go-gitea/gitea/assets/75628309/bbc024c4-2bc0-4fb0-9dc8-a435c6f6073a"> Upon inspecting the code, I found that the assignments for these headers are the same. <img width="1020" alt="image" src="https://github.com/go-gitea/gitea/assets/75628309/8125ce0d-1a0b-4884-8d25-2096c351673a">

GiteaMirror added the type/proposal label 2025-11-02 09:33:32 -06:00

GiteaMirror commented

2025-11-02 09:33:33 -06:00

@Makonike commented on GitHub (Jul 20, 2023):

I would be willing to help with the implementation, but I still need a bit of assistance.

@Makonike commented on GitHub (Jul 20, 2023): I would be willing to help with the implementation, but I still need a bit of assistance.

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