github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-16 21:23:02 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Wording in "last changed date" #2324

New Issue
Closed
opened 2025-11-02 04:32:52 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 04:32:52 -06:00
Owner
Copy Link

Originally created by @hoellen on GitHub (Sep 12, 2018).

  • Gitea version: d918e63
  • Git version: 2.18
  • Operating system: CentOS
  • 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

If the last changed date of a file in repository is more then 1.5 years ago, then it should say "2 years ago", instead of "1 year ago".
In the example screenshot you can see the last changes on the file has been made on 26 Nov 2016. And that is in my opinion more "2 years ago" then "1 year" atm.

Screenshots

grafik

Originally created by @hoellen on GitHub (Sep 12, 2018). - Gitea version: d918e63 - Git version: 2.18 - Operating system: CentOS - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description If the last changed date of a file in repository is more then 1.5 years ago, then it should say "2 years ago", instead of "1 year ago". In the example screenshot you can see the last changes on the file has been made on 26 Nov 2016. And that is in my opinion more "2 years ago" then "1 year" atm. ## Screenshots ![grafik](https://user-images.githubusercontent.com/11299996/45405031-9accdc00-b661-11e8-98ee-f14e14ed5703.png)
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 04:32:52 -06:00
GiteaMirror commented 2025-11-02 04:32:53 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 12, 2018):

I think there already was issue about that

@lafriks commented on GitHub (Sep 12, 2018): I think there already was issue about that
GiteaMirror commented 2025-11-02 04:32:53 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 9, 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 (Jan 9, 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 04:32:53 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 11, 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 (Mar 11, 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.
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#2324
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?