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

Count on Projects tab (clarify or remove?) #10178

New Issue
Closed
opened 2025-11-02 09:00:20 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 09:00:20 -06:00
Owner
Copy Link

Originally created by @JVimes on GitHub (Jan 29, 2023).

Feature Description

I'm not sure about this number:

image

It looks like an unread/open count. It makes sense for things that need to be addressed, but I think projects live indefinitely.

Screenshots

No response

Originally created by @JVimes on GitHub (Jan 29, 2023). ### Feature Description I'm not sure about this number: ![image](https://user-images.githubusercontent.com/6148201/215351697-994652aa-2bd6-48e5-9a40-32de6373bed6.png) It looks like an unread/open count. It makes sense for things that need to be addressed, but I think projects live indefinitely. ### Screenshots _No response_
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 09:00:20 -06:00
GiteaMirror commented 2025-11-02 09:00:21 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jan 29, 2023):

It is intended as number of open projects.
I don't think it should be removed.

@delvh commented on GitHub (Jan 29, 2023): It is intended as `number of open projects`. I don't think it should be removed.
GiteaMirror commented 2025-11-02 09:00:21 -06:00
Author
Owner
Copy Link

@JVimes commented on GitHub (Jan 29, 2023):

Can you help me understand the value to the user?

@JVimes commented on GitHub (Jan 29, 2023): Can you help me understand the value to the user?
GiteaMirror commented 2025-11-02 09:00:21 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Jan 29, 2023):

  • Consistency with the other tabs
  • indicates whether the project uses projects and how they use it
    (0 → No projects,1 → One project for everything, 2+ → custom project structure)

would be my spontaneous guess?

@delvh commented on GitHub (Jan 29, 2023): - Consistency with the other tabs - indicates whether the project uses projects and how they use it (`0 → No projects`,`1 → One project for everything`, `2+ → custom project structure`) would be my spontaneous guess?
GiteaMirror commented 2025-11-02 09:00:22 -06:00
Author
Owner
Copy Link

@JVimes commented on GitHub (Jan 29, 2023):

Okay. I think it's styled to draw attention like an unread count. It makes me feel like there's something outstanding I need to address. As an informational element I think it's got too prominent of a placement (right on the tab, always visible, contrasting background square).

@JVimes commented on GitHub (Jan 29, 2023): Okay. I think it's styled to draw attention like an unread count. It makes me feel like there's something outstanding I need to address. As an informational element I think it's got too prominent of a placement (right on the tab, always visible, contrasting background square).
GiteaMirror commented 2025-11-02 09:00:22 -06:00
Author
Owner
Copy Link

@fsiddi commented on GitHub (Jan 31, 2023):

Suggesting #22687 to address this.

@fsiddi commented on GitHub (Jan 31, 2023): Suggesting #22687 to address this.
GiteaMirror commented 2025-11-02 09:00:22 -06:00
Author
Owner
Copy Link

@JVimes commented on GitHub (Jan 31, 2023):

Thanks @fsiddi , that would address my main concern.

@JVimes commented on GitHub (Jan 31, 2023): Thanks @fsiddi , that would address my main concern.
GiteaMirror commented 2025-11-02 09:00:22 -06:00
Author
Owner
Copy Link

@fsiddi commented on GitHub (Feb 9, 2023):

This has been addressed, so I suggest to close the issue.

@fsiddi commented on GitHub (Feb 9, 2023): This has been addressed, so I suggest to close the issue.
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/feature 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#10178
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?