github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Repository live search #11365

New Issue
Open
opened 2025-11-02 09:35:37 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 09:35:37 -06:00
Owner
Copy Link

Originally created by @KazzmanK on GitHub (Jul 29, 2023).

Feature Description

On the http://root_path on the right pane repositories search is live, as you type
but on http://root_path/organization , repository list is a main UI element, search is not live.
My proposal is to make repository search on http://root_path/organization live, as you type.

Screenshots

No response

Originally created by @KazzmanK on GitHub (Jul 29, 2023). ### Feature Description On the http://root_path on the right pane repositories search is live, as you type but on http://root_path/organization , repository list is a main UI element, search is not live. My proposal is to make repository search on http://root_path/organization live, as you type. ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 09:35:37 -06:00
GiteaMirror commented 2025-11-02 09:35:37 -06:00
Author
Owner
Copy Link

@puni9869 commented on GitHub (Jul 29, 2023):

Performance will hit if we support the live search.

@puni9869 commented on GitHub (Jul 29, 2023): Performance will hit if we support the live search.
GiteaMirror commented 2025-11-02 09:35:38 -06:00
Author
Owner
Copy Link

@KazzmanK commented on GitHub (Jul 29, 2023):

I'm not sure what you are talking about, because full repository list is already on client, there is no need to recall it from back again and again.
But even if filtering will be done at back end, I see little to nothing computation workload to send back dozen or even few hundred of records. My recent project sends via rest api tens of thousands records in a second.
I have created another similar issue #26227, if you can give me a hint of how to catch possible queries, or share these queries , I can play around to form my own opinion.

@KazzmanK commented on GitHub (Jul 29, 2023): I'm not sure what you are talking about, because full repository list is already on client, there is no need to recall it from back again and again. But even if filtering will be done at back end, I see little to nothing computation workload to send back dozen or even few hundred of records. My recent project sends via rest api tens of thousands records in a second. I have created another similar issue [#26227](https://github.com/go-gitea/gitea/issues/26227), if you can give me a hint of how to catch possible queries, or share these queries , I can play around to form my own opinion.
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#11365
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?