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

Milestones of archived Repositories still open #8347

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

Originally created by @kimdre on GitHub (Jan 12, 2022).

Gitea Version

1.15.9

Operating System

No response

Browser Version

Brave 1.34.80

Can you reproduce the bug on the Gitea demo site?

Yes

Description

Any Milestones of archived Repositories still appear as "Open" in the Milestones-Tab (BASE_URL/milestones).
Maybe those should get their own section.

Screenshots

Milestone Tab
Milestone View
Milestone Issue

Originally created by @kimdre on GitHub (Jan 12, 2022). ### Gitea Version 1.15.9 ### Operating System _No response_ ### Browser Version Brave 1.34.80 ### Can you reproduce the bug on the Gitea demo site? Yes ### Description Any Milestones of archived Repositories still appear as "_Open_" in the Milestones-Tab (BASE_URL/milestones). Maybe those should get their own section. ### Screenshots ![Milestone Tab](https://user-images.githubusercontent.com/27567533/149205777-082da055-b21c-42a5-9dc1-eac31f2f6c33.png) ![Milestone View](https://user-images.githubusercontent.com/27567533/149205784-069aca28-223c-4430-ae84-5f42e34e3c34.png) ![Milestone Issue](https://user-images.githubusercontent.com/27567533/149205792-cbc62ec7-3b09-41b6-ac4a-2733db507f75.png)
GiteaMirror added the type/bug label 2025-11-02 08:03:16 -06:00
GiteaMirror commented 2025-11-02 08:03:17 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 13, 2022):

They could be open but should not be editable.

@lunny commented on GitHub (Jan 13, 2022): They could be open but should not be editable.
GiteaMirror commented 2025-11-02 08:03:17 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (May 21, 2022):

I am not quite sure what you mean:
I also just noticed this, and I think it is not exactly user-friendly.
Normally, if a repo is archived, you don't want it to be displayed in your list of milestones because there is no more development on this repo.
But the purpose of this list should be to notify you where you have (what) work to do...

@delvh commented on GitHub (May 21, 2022): I am not quite sure what you mean: I also just noticed this, and I think it is not exactly user-friendly. Normally, if a repo is archived, you don't want it to be displayed in your list of milestones because there is no more development on this repo. But the purpose of this list should be to notify you where you have (what) work to do...
GiteaMirror commented 2025-11-02 08:03:17 -06:00
Author
Owner
Copy Link

@kimdre commented on GitHub (May 21, 2022):

I think it would be easier if they got their own tab so you can browse between open, closed and archived issues.

@kimdre commented on GitHub (May 21, 2022): I think it would be easier if they got their own tab so you can browse between open, closed and archived issues.
GiteaMirror commented 2025-11-02 08:03:17 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (May 21, 2022):

Or at least some sort of checkbox to switch between displaying archived repos as well.

@delvh commented on GitHub (May 21, 2022): Or at least some sort of checkbox to switch between displaying archived repos as well.
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/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#8347
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?