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

ArgoCD: Webhook processing failed: json: cannot unmarshal string into Go struct field .repository.created_at of type int64 #13597

New Issue
Closed
opened 2025-11-02 10:47:37 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 10:47:37 -06:00
Owner
Copy Link

Originally created by @volker-raschek on GitHub (Oct 14, 2024).

Description

I've deployed Gitea v1.22.1 via the official helm chart into my kubernetes cluster. In my cluster is also running ArgoCD to manage updates and deployments via GitDevOps.

The documentation of ArgoCD describes how to configure a WebHook to inform about new git commits pushed into a git repository - a dedicated documentation how to configure a WebHook for Gitea is missing.

Nevertheless, I tried to configure the WebHook like the example of GitHub. When I execute a test, Gitea receive an HTTP Statuscode 400 with the error message Webhook processing failed: json: cannot unmarshal string into Go struct field .repository.created_at of type int64.

  1. Please provide a clear documentation on ArgoCD how to configure a WebHook in Gitea correctly.
  2. Try to reproduce the error with an public ArgoCD instance. I've currently installed ArgoCD 2.12.4 via the helm chart v7.6.8.

Gitea Version

1.22.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Bildschirmfoto vom 2024-10-14 21-32-40
Bildschirmfoto vom 2024-10-14 21-33-22

Git Version

No response

Operating System

No response

How are you running Gitea?

As helm chart v10.4.0

Database

PostgreSQL

Originally created by @volker-raschek on GitHub (Oct 14, 2024). ### Description I've deployed Gitea v1.22.1 via the official helm chart into my kubernetes cluster. In my cluster is also running ArgoCD to manage updates and deployments via GitDevOps. The [documentation](https://argo-cd.readthedocs.io/en/latest/operator-manual/webhook/) of ArgoCD describes how to configure a WebHook to inform about new git commits pushed into a git repository - a dedicated documentation how to configure a WebHook for Gitea is missing. Nevertheless, I tried to configure the WebHook like the example of GitHub. When I execute a test, Gitea receive an HTTP Statuscode 400 with the error message `Webhook processing failed: json: cannot unmarshal string into Go struct field .repository.created_at of type int64`. 1. Please provide a clear documentation on ArgoCD how to configure a WebHook in Gitea correctly. 2. Try to reproduce the error with an public ArgoCD instance. I've currently installed ArgoCD 2.12.4 via the helm chart v7.6.8. ### Gitea Version 1.22.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![Bildschirmfoto vom 2024-10-14 21-32-40](https://github.com/user-attachments/assets/91bda3eb-988d-4125-9d68-ef66d3abdd24) ![Bildschirmfoto vom 2024-10-14 21-33-22](https://github.com/user-attachments/assets/92c1c46f-d7a3-4851-aea8-032da1c2cc97) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? As helm chart v10.4.0 ### Database PostgreSQL
GiteaMirror added the issue/needs-feedbacktype/upstream labels 2025-11-02 10:47:37 -06:00
GiteaMirror commented 2025-11-02 10:47:38 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 15, 2024):

It seems that the create_at field is string-type since 2016/2017, but ArgoCD are not able to parse it correctly?

image

@wxiaoguang commented on GitHub (Oct 15, 2024): It seems that the `create_at` field is string-type since 2016/2017, but ArgoCD are not able to parse it correctly? ![image](https://github.com/user-attachments/assets/de422e7c-e04a-4720-88ce-3e8ececc918d)
GiteaMirror commented 2025-11-02 10:47:38 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 15, 2024):

The documentation of ArgoCD describes how to configure a WebHook to inform about new git commits pushed into a git repository - a dedicated documentation how to configure a WebHook for Gitea is missing.
Nevertheless, I tried to configure the WebHook like the example of GitHub.

It seems that the problem is ArgoCD lacks Gitea support. Gitea is not GitHub and the API definitions are different in many ways.

@wxiaoguang commented on GitHub (Oct 15, 2024): > The [documentation](https://argo-cd.readthedocs.io/en/latest/operator-manual/webhook/) of ArgoCD describes how to configure a WebHook to inform about new git commits pushed into a git repository - a dedicated documentation how to configure a WebHook for Gitea is missing. > Nevertheless, I tried to configure the WebHook like the example of GitHub. It seems that the problem is ArgoCD lacks Gitea support. Gitea is not GitHub and the API definitions are different in many ways.
GiteaMirror commented 2025-11-02 10:47:38 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 21, 2024):

Have you tried to use Gogs as the webhook? Maybe the Gogs one works, since Gitea hard-forked from Gogs since 2016.

@wxiaoguang commented on GitHub (Oct 21, 2024): Have you tried to use Gogs as the webhook? Maybe the Gogs one works, since Gitea hard-forked from Gogs since 2016.
GiteaMirror commented 2025-11-02 10:47:38 -06:00
Author
Owner
Copy Link

@volker-raschek commented on GitHub (Nov 4, 2024):

Hi @wxiaoguang,
no I have not tried it with Gogs, yet. I will test it the next days and will report my test results.

@volker-raschek commented on GitHub (Nov 4, 2024): Hi @wxiaoguang, no I have not tried it with Gogs, yet. I will test it the next days and will report my test results.
GiteaMirror commented 2025-11-02 10:47:39 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Dec 4, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Dec 4, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:
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/needs-feedback type/upstream
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#13597
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?