GPG signed commits incorrectly listed as invalid #4921

New Issue

GiteaMirror · 2025-11-02T06:07:25-06:00

GiteaMirror commented

2025-11-02 06:07:25 -06:00

Originally created by @zeripath on GitHub (Feb 22, 2020).

Gitea version (or commit ref): master
Git version:
Operating system: linux

Description

Go-Git incorrectly reads dates on which could be within the local timezone. An example being that a commit with date:

1579639200 +0100

Within the UK will be incorrectly parsed and re-represented as:

1579639200 +0000

A fix has been pushed to go-git as https://github.com/src-d/go-git/pull/1291

Originally created by @zeripath on GitHub (Feb 22, 2020). - Gitea version (or commit ref): master - Git version: - Operating system: linux ## Description Go-Git incorrectly reads dates on which could be within the local timezone. An example being that a commit with date: ``` 1579639200 +0100 ``` Within the UK will be incorrectly parsed and re-represented as: ``` 1579639200 +0000 ``` A fix has been pushed to go-git as https://github.com/src-d/go-git/pull/1291

GiteaMirror added the type/bug label 2025-11-02 06:07:25 -06:00

GiteaMirror closed this issue

2025-11-02 06:07:26 -06:00

GiteaMirror commented

2025-11-02 06:07:27 -06:00

@zeripath commented on GitHub (Feb 22, 2020):

A likely workaround would be to run your server in the UTC TZ.

@zeripath commented on GitHub (Feb 22, 2020): A likely workaround would be to run your server in the UTC TZ.

GiteaMirror referenced this issue

2025-11-02 13:59:34 -06:00

[PR #4921] [MERGED] Optimize pulls merging #17548

Sign in to join this conversation.