github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-26 22:10:35 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Can I change git command timeout through config file ? #1485

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

Originally created by @comicfans on GitHub (Jan 31, 2018).

Currently I have a huge git repo with many binaries , for easier use, we use web interface to download package (instead of git client or lfs ), and I'm facing git command timeout problem original issue here

Recently I've read that https://github.com/go-gitea/git/pull/104 is merged to makes git command timeout configurable , but I can not find any updates in config docs or gitea commit history, I wonder if this config option still not implemented on gitea side ?

Originally created by @comicfans on GitHub (Jan 31, 2018). Currently I have a huge git repo with many binaries , for easier use, we use web interface to download package (instead of git client or lfs ), and I'm facing git command timeout problem [original issue here](https://github.com/gogits/gogs/issues/4903) Recently I've read that https://github.com/go-gitea/git/pull/104 is merged to makes git command timeout configurable , but I can not find any updates in config docs or gitea commit history, I wonder if this config option still not implemented on gitea side ?
GiteaMirror added the issue/confirmedtype/enhancement labels 2025-11-02 04:02:11 -06:00
GiteaMirror commented 2025-11-02 04:02:11 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 31, 2018):

I think someone could send a PR to add a option on config.ini to do that. It's a small PR and easy enough to do.

@lunny commented on GitHub (Jan 31, 2018): I think someone could send a PR to add a option on `config.ini` to do that. It's a small PR and easy enough to do.
GiteaMirror commented 2025-11-02 04:02:11 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 8, 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 (Feb 8, 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/enhancement
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#1485
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?