You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Pull Request view serves as a TODO list of sorts. It's quite nice. However, it gets cluttered up when partial tickets are still open when a dead project is archived.
Steps to reproduce:
Have a team (org) with a repository
One of your team members opens a PR
Comment on the PR
Archive the repository
Open the Pull Request view
Choose the "Reviewed by you" menu option
See the PR that can no longer be closed
I don't know if this affects all of the Pull Request menu options. While writing up this report, I noticed that it affects the Issues ("Mentioning you" and "Created by you") views, too.
These things are not actionable, and I guess they will live forever. So, could we exclude them from the lists and the counts?
I think a workaround is to close everything manually before archiving a dead project repo. Is that what we should do?
Thanks!
Gitea Version
1.22.4
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
PR view showing a partial PR in a dead (archived) repo:
Issue view showing multiple open issues from that same dead (archived) repo:
Git Version
No response
Operating System
No response
How are you running Gitea?
self hosted container
Database
PostgreSQL
The text was updated successfully, but these errors were encountered:
Description
The Pull Request view serves as a TODO list of sorts. It's quite nice. However, it gets cluttered up when partial tickets are still open when a dead project is archived.
Steps to reproduce:
I don't know if this affects all of the Pull Request menu options. While writing up this report, I noticed that it affects the Issues ("Mentioning you" and "Created by you") views, too.
These things are not actionable, and I guess they will live forever. So, could we exclude them from the lists and the counts?
I think a workaround is to close everything manually before archiving a dead project repo. Is that what we should do?
Thanks!
Gitea Version
1.22.4
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
PR view showing a partial PR in a dead (archived) repo:
Issue view showing multiple open issues from that same dead (archived) repo:
Git Version
No response
Operating System
No response
How are you running Gitea?
self hosted container
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: