Webhooks don't work with deployment keys #2533

Closed
opened 2025-11-02 04:39:39 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @tarelda on GitHub (Nov 14, 2018).

  • Gitea version (or commit ref): 6efdcae
  • Git version: 2.15.2
  • Operating system: Alpine Linux inside Docker
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When trying to push into repository using RW deployment key webhooks are not triggered whilst with normal user's key everything works fine.

Screenshots

Originally created by @tarelda on GitHub (Nov 14, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 6efdcae - Git version: 2.15.2 - Operating system: Alpine Linux inside Docker - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description When trying to push into repository using RW deployment key webhooks are not triggered whilst with normal user's key everything works fine. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/bug label 2025-11-02 04:39:39 -06:00
Author
Owner

@techknowlogick commented on GitHub (Dec 6, 2018):

Related to #3795

@techknowlogick commented on GitHub (Dec 6, 2018): Related to #3795
Author
Owner

@stale[bot] commented on GitHub (Feb 5, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 5, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@zeripath commented on GitHub (Feb 5, 2019):

Should now be fixed.

@zeripath commented on GitHub (Feb 5, 2019): Should now be fixed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2533