github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-11 01:07:59 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Tag push creates webhook with empty commits and head_commit #8292

New Issue
Closed
opened 2025-11-02 08:01:17 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 08:01:17 -06:00
Owner
Copy Link

Originally created by @DoLearnWhileAlive on GitHub (Dec 27, 2021).

Gitea Version

1.15.8

Git Version

2.33.1

Operating System

Windows Server 2016

How are you running Gitea?

based on gitea-1.15.8-windows-4.0-amd64.exe as Windows Service

Database

SQLite

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Description

Creating a new tag for a gitea repo creates a webhook with empty commits and head_commit. See example from gitea demo site:

{
  "ref": "refs/tags/v1.1.1",
  "before": "0000000000000000000000000000000000000000",
  "after": "3f150d39b92dd50cdd0248f5edea5767c2172584",
  "compare_url": "https://try.gitea.io/",
  "commits": [],
  "head_commit": null,
  "repository": {
  ...

I have an on-prem gitea instance connected with on-prem AppVeyor server. AppVeyor can't create new builds if commits and head_commit are empty, see also open issue on AppVeyor: appveyor/ci#3765

Screenshots

No response

Originally created by @DoLearnWhileAlive on GitHub (Dec 27, 2021). ### Gitea Version 1.15.8 ### Git Version 2.33.1 ### Operating System Windows Server 2016 ### How are you running Gitea? based on gitea-1.15.8-windows-4.0-amd64.exe as Windows Service ### Database SQLite ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Description Creating a new tag for a gitea repo creates a webhook with empty `commits` and `head_commit`. See example from gitea demo site: ``` { "ref": "refs/tags/v1.1.1", "before": "0000000000000000000000000000000000000000", "after": "3f150d39b92dd50cdd0248f5edea5767c2172584", "compare_url": "https://try.gitea.io/", "commits": [], "head_commit": null, "repository": { ... ``` I have an on-prem gitea instance connected with on-prem AppVeyor server. AppVeyor can't create new builds if `commits` and `head_commit` are empty, see also open issue on AppVeyor: appveyor/ci#3765 ### Screenshots _No response_
GiteaMirror commented 2025-11-02 08:01:19 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Dec 31, 2021):

@DoLearnWhileAlive Does AppVeyor work now?

@KN4CK3R commented on GitHub (Dec 31, 2021): @DoLearnWhileAlive Does AppVeyor work now?
GiteaMirror commented 2025-11-02 08:01:19 -06:00
Author
Owner
Copy Link

@DoLearnWhileAlive commented on GitHub (Jan 3, 2022):

Just tested newest Gitea main build (1.16.0+dev-785-g496acbe9e) and AppVeyor is still not triggering a new build for a new tag. AppVeyor seems to expect both commits and head_commit to be defined.

@DoLearnWhileAlive commented on GitHub (Jan 3, 2022): Just tested newest Gitea main build (1.16.0+dev-785-g496acbe9e) and AppVeyor is still not triggering a new build for a new tag. AppVeyor seems to expect both `commits` and `head_commit` to be defined.
GiteaMirror commented 2025-11-02 08:01:19 -06:00
Author
Owner
Copy Link

@DoLearnWhileAlive commented on GitHub (Jan 3, 2022):

@KN4CK3R AppVeyor Server was updated with version 7.0.3134 to support head_commit in the webhook payload. With that change AppVeyor Server is creating a build for a Gitea tag webhook again. See also appveyor/ci#3765.
Thanks for fixing the Gitea part!

@DoLearnWhileAlive commented on GitHub (Jan 3, 2022): @KN4CK3R AppVeyor Server was updated with version 7.0.3134 to support `head_commit` in the webhook payload. With that change AppVeyor Server is creating a build for a Gitea tag webhook again. See also appveyor/ci#3765. Thanks for fixing the Gitea part!
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
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#8292
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?