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

Repository size and languages percentage doesn't update when repo updated manually #8307

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

Originally created by @dehghani-mehdi on GitHub (Jan 2, 2022).

Gitea Version

latest

Git Version

2.27.0

Operating System

Windows 10

How are you running Gitea?

By running Gitea via command-line

Database

SQLite

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

When I push offline/manually repository size and languages percentage doesn't update, by offline I mean copy bare repository from somewhere else and paste to repo location, not by pushing to http://localhost:....

Screenshots

No response

Originally created by @dehghani-mehdi on GitHub (Jan 2, 2022). ### Gitea Version latest ### Git Version 2.27.0 ### Operating System Windows 10 ### How are you running Gitea? By running `Gitea` via command-line ### Database SQLite ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description When I push offline/manually repository size and languages percentage doesn't update, by offline I mean copy bare repository from somewhere else and paste to repo location, not by pushing to `http://localhost:....` ### Screenshots _No response_
GiteaMirror commented 2025-11-02 08:01:48 -06:00
Author
Owner
Copy Link

@Gusted commented on GitHub (Jan 2, 2022):

I think this is working as intended from my perspective. As I'm pretty sure that Gitea doesn't allow nor support that users are messing around with the repo's that Gitea is hosting. As a lot of functionality(like language and size) isn't generated on-demand, but they are generated when their are new commits on the main branch.

@Gusted commented on GitHub (Jan 2, 2022): I think this is working as intended from my perspective. As I'm pretty sure that Gitea doesn't allow nor support that users are messing around with the repo's that Gitea is hosting. As a lot of functionality(like language and size) isn't generated on-demand, but they are generated when their are new commits on the main branch.
GiteaMirror commented 2025-11-02 08:01:48 -06:00
Author
Owner
Copy Link

@dehghani-mehdi commented on GitHub (Jan 2, 2022):

Gitea shows all commits and files correctly, even tho I manually update the repo.

@dehghani-mehdi commented on GitHub (Jan 2, 2022): Gitea shows all commits and files correctly, even tho I manually update the repo.
GiteaMirror commented 2025-11-02 08:01:48 -06:00
Author
Owner
Copy Link

@Gusted commented on GitHub (Jan 2, 2022):

Gitea shows all commits and files correctly, even tho I manually update the repo.

Well, that doesn't imply that it's allowed or supported. I'm against it, as allowing this can cause for a lot of undefined behavior. Maybe some other maintainer want's to shed some light 🤷🏽

@Gusted commented on GitHub (Jan 2, 2022): > Gitea shows all commits and files correctly, even tho I manually update the repo. Well, that doesn't imply that it's allowed or supported. I'm against it, as allowing this can cause for a lot of undefined behavior. Maybe some other maintainer want's to shed some light 🤷🏽
GiteaMirror commented 2025-11-02 08:01:48 -06:00
Author
Owner
Copy Link

@dehghani-mehdi commented on GitHub (Jan 2, 2022):

Other maintainer can set the remote url to file://path/to/repository.git, as I did, in fact we currently working this way without any problem.

I can make a fake commit and push to http://localhost:...., so Gitea update repo info (e.g languages and size), but I'm not happy with it. that's why I filed this issue.

@dehghani-mehdi commented on GitHub (Jan 2, 2022): Other maintainer can set the remote url to `file://path/to/repository.git`, as I did, in fact we currently working this way without any problem. I can make a fake commit and push to `http://localhost:....`, so Gitea update repo info (e.g languages and size), but I'm not happy with it. that's why I filed this issue.
GiteaMirror commented 2025-11-02 08:01:49 -06:00
Author
Owner
Copy Link

@Gusted commented on GitHub (Jan 2, 2022):

so Gitea update repo info (e.g languages and size), but I'm not happy with it. that's why I filed this issue.

Well you could manually update it by going to the settings page of the repo and then click on the Add to the Re-Index queue

image

@Gusted commented on GitHub (Jan 2, 2022): > so Gitea update repo info (e.g languages and size), but I'm not happy with it. that's why I filed this issue. Well you could manually update it by going to the settings page of the repo and then click on the `Add to the Re-Index queue` ![image](https://user-images.githubusercontent.com/25481501/147882474-d5cab459-c5fd-46c0-b1ed-9c45c034f30d.png)
GiteaMirror commented 2025-11-02 08:01:49 -06:00
Author
Owner
Copy Link

@dehghani-mehdi commented on GitHub (Jan 2, 2022):

I can not see Code Statistics Indexer section. all I have is this:

image

@dehghani-mehdi commented on GitHub (Jan 2, 2022): I can not see `Code Statistics Indexer` section. all I have is this: ![image](https://user-images.githubusercontent.com/9152330/147882561-a1ce6c33-fd5d-4074-a937-74e4e0ce1d6a.png)
GiteaMirror commented 2025-11-02 08:01:49 -06:00
Author
Owner
Copy Link

@Gusted commented on GitHub (Jan 2, 2022):

https://github.com/go-gitea/gitea/pull/17494 It will be added in the next release.

@Gusted commented on GitHub (Jan 2, 2022): https://github.com/go-gitea/gitea/pull/17494 It will be added in the next release.
GiteaMirror commented 2025-11-02 08:01:49 -06:00
Author
Owner
Copy Link

@dehghani-mehdi commented on GitHub (Jan 2, 2022):

By doing that, the language and size info will be updated correctly?

@dehghani-mehdi commented on GitHub (Jan 2, 2022): By doing that, the language and size info will be updated correctly?
GiteaMirror commented 2025-11-02 08:01:49 -06:00
Author
Owner
Copy Link

@Gusted commented on GitHub (Jan 2, 2022):

Yap. It then takes the latest commit(doesn't mater if it was pushed online or offline).

@Gusted commented on GitHub (Jan 2, 2022): Yap. It then takes the latest commit(doesn't mater if it was pushed online or offline).
GiteaMirror commented 2025-11-02 08:01:50 -06:00
Author
Owner
Copy Link

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

Maybe that's not usefull for repository size ...

@a1012112796 commented on GitHub (Jan 3, 2022): Maybe that's not usefull for repository size ...
GiteaMirror commented 2025-11-02 08:01:50 -06:00
Author
Owner
Copy Link

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

Maybe that's not usefull for repository size ...

🤷🏽 I'm pretty sure that gitea doesn't support nor handle that users are messing around with the repo's under the data folder. So it's just own-risk and what works, that works.

@Gusted commented on GitHub (Jan 3, 2022): > Maybe that's not usefull for repository size ... 🤷🏽 I'm pretty sure that gitea doesn't support nor handle that users are messing around with the repo's under the data folder. So it's just own-risk and what works, that works.
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#8307
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?