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

Time bug on mirror repository #3134

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

Originally created by @lunny on GitHub (Apr 3, 2019).

Gitea's mirror repository display three days after.
image

Github display just now on the same file.
image

Repo link: https://gitea.com/lunny/go-astilectron-bundler

Originally created by @lunny on GitHub (Apr 3, 2019). Gitea's mirror repository display `three days after`. ![image](https://user-images.githubusercontent.com/81045/55486418-df03e600-565e-11e9-9dc5-344ab75f62f3.png) Github display `just now` on the same file. ![image](https://user-images.githubusercontent.com/81045/55486494-fcd14b00-565e-11e9-8538-aade7f93ec14.png) Repo link: https://gitea.com/lunny/go-astilectron-bundler
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 05:01:42 -06:00
GiteaMirror commented 2025-11-02 05:01:43 -06:00
Author
Owner
Copy Link

@mrsdizzie commented on GitHub (Apr 3, 2019):

The date on that file at Github is April 6th, 2019 which is 3 days from today
Screen Shot 2019-04-03 at 10 50 42 AM

Magic ;) If Gitea changed to say "just now", it would also probably still say "just now" for the next 3 days (and I bet GitHub does too). Also on this screen Github says "3 days from now" too:

https://github.com/asticode/go-astilectron-bundler/blob/master/bundler.go

Gitea should maybe change to never show a time being "in the future" in this case, but the commit time is bad here and the code itself isn't doing anything wrong.

@mrsdizzie commented on GitHub (Apr 3, 2019): The date on that file at Github is April 6th, 2019 which *is* 3 days from today <img width="197" alt="Screen Shot 2019-04-03 at 10 50 42 AM" src="https://user-images.githubusercontent.com/1669571/55488954-02974400-55ff-11e9-88da-ae3fff1e374f.png"> Magic ;) If Gitea changed to say "just now", it would also probably still say "just now" for the next 3 days (and I bet GitHub does too). Also on this screen Github says "3 days from now" too: https://github.com/asticode/go-astilectron-bundler/blob/master/bundler.go Gitea should maybe change to never show a time being "in the future" in this case, but the commit time is bad here and the code itself isn't doing anything wrong.
GiteaMirror commented 2025-11-02 05:01:43 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jun 2, 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 (Jun 2, 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.
GiteaMirror commented 2025-11-02 05:01:43 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 26, 2023):

I think this has been resolved by #23988

@lunny commented on GitHub (Apr 26, 2023): I think this has been resolved by #23988
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/confirmed type/bug
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#3134
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?