github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Suggest to shorten the time of stale #5152

New Issue
Closed
opened 2025-11-02 06:16:08 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 06:16:08 -06:00
Owner
Copy Link

Originally created by @a1012112796 on GitHub (Mar 30, 2020).

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • 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

Hello, now the stale time is two month. I think it would be more usefull to cut it down to one month or even twenty days. because I think the stale is a way to notify users to take care of the issue or pull request which hase been lost focus. but I think two moths is too long to do this thing. the reason why I think about this thing is this PR (#10492) . It haven't be reviewed from 27 Feb to four days before. The author may be have lost interest about it . thats my thinks , thanks .

Originally created by @a1012112796 on GitHub (Mar 30, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: - Operating system: - 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 Hello, now the stale time is two month. I think it would be more usefull to cut it down to one month or even twenty days. because I think the stale is a way to notify users to take care of the issue or pull request which hase been lost focus. but I think two moths is too long to do this thing. the reason why I think about this thing is this PR (#10492) . It haven't be reviewed from 27 Feb to four days before. The author may be have lost interest about it . thats my thinks , thanks .
GiteaMirror added the type/proposal label 2025-11-02 06:16:08 -06:00
GiteaMirror commented 2025-11-02 06:16:09 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Apr 6, 2020):

stale is sometime anoying but it remid you, so 👍

@6543 commented on GitHub (Apr 6, 2020): stale is sometime anoying but it remid you, so :+1:
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 type/proposal
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#5152
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?