Search field in header #13859

Open
opened 2025-11-02 10:55:21 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @vexvec on GitHub (Dec 19, 2024).

Feature Description

Please add a search field in header, like Github has or as shown in the screenshot (Schematic search field).
I have this, but everytime you update the layout my custom template breaks...

Behavior of the field should be as follows:
TERM + Enter: you land on the repo search site with the given term
org:TERM + Enter: you land on the org search site with the given term searched
code: TERM + Enter: You land on the code search site with the given term searched.

It makes accessibility so much better. Think you are in a repo but want to chickly search for another. Without this functionality you always have to go to the dashboard or to explore.

Screenshots

Screenshot_2024-12-19_21-01-51

Originally created by @vexvec on GitHub (Dec 19, 2024). ### Feature Description Please add a search field in header, like Github has or as shown in the screenshot (Schematic search field). I have this, but everytime you update the layout my custom template breaks... Behavior of the field should be as follows: TERM + Enter: you land on the repo search site with the given term org:TERM + Enter: you land on the org search site with the given term searched code: TERM + Enter: You land on the code search site with the given term searched. It makes accessibility so much better. Think you are in a repo but want to chickly search for another. Without this functionality you always have to go to the dashboard or to explore. ### Screenshots ![Screenshot_2024-12-19_21-01-51](https://github.com/user-attachments/assets/2bd9da03-a56d-4d44-a725-88680c40b072)
GiteaMirror added the type/proposaltopic/ui labels 2025-11-02 10:55:21 -06:00
Author
Owner

@vexvec commented on GitHub (Jul 17, 2025):

@wxiaoguang could you please take a look at this proposal? I would appreciate it very much.

@vexvec commented on GitHub (Jul 17, 2025): @wxiaoguang could you please take a look at this proposal? I would appreciate it very much.
Author
Owner

@wxiaoguang commented on GitHub (Jul 18, 2025):

It doesn't seem to be as simple as a UI change, and TBH I don't have much time on it. Maybe someone who has interests could try to implement it.

@wxiaoguang commented on GitHub (Jul 18, 2025): It doesn't seem to be as simple as a UI change, and TBH I don't have much time on it. Maybe someone who has interests could try to implement it.
Author
Owner

@vexvec commented on GitHub (Jul 18, 2025):

If I implement it, would you accept a PR?


From: wxiaoguang @.>
Sent: Friday, July 18, 2025 3:04:38 AM
To: go-gitea/gitea @.
>
Cc: ace @.>; Author @.>
Subject: Re: [go-gitea/gitea] Search field in header (Issue #32919)

[https://avatars.githubusercontent.com/u/2114189?s=20&v=4]wxiaoguang left a comment (go-gitea/gitea#32919)https://github.com/go-gitea/gitea/issues/32919#issuecomment-3086194718

It doesn't seem to be as simple as a UI change, and TBH I don't have much time on it. Maybe someone who has interests could try to implement it.


Reply to this email directly, view it on GitHubhttps://github.com/go-gitea/gitea/issues/32919#issuecomment-3086194718, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AITUPUXHO3H2LZBWKRDMBF33JBB2NAVCNFSM6AAAAABT5YQSNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBWGE4TINZRHA.
You are receiving this because you authored the thread.Message ID: @.***>

@vexvec commented on GitHub (Jul 18, 2025): If I implement it, would you accept a PR? ________________________________ From: wxiaoguang ***@***.***> Sent: Friday, July 18, 2025 3:04:38 AM To: go-gitea/gitea ***@***.***> Cc: ace ***@***.***>; Author ***@***.***> Subject: Re: [go-gitea/gitea] Search field in header (Issue #32919) [https://avatars.githubusercontent.com/u/2114189?s=20&v=4]wxiaoguang left a comment (go-gitea/gitea#32919)<https://github.com/go-gitea/gitea/issues/32919#issuecomment-3086194718> It doesn't seem to be as simple as a UI change, and TBH I don't have much time on it. Maybe someone who has interests could try to implement it. — Reply to this email directly, view it on GitHub<https://github.com/go-gitea/gitea/issues/32919#issuecomment-3086194718>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AITUPUXHO3H2LZBWKRDMBF33JBB2NAVCNFSM6AAAAABT5YQSNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBWGE4TINZRHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@wxiaoguang commented on GitHub (Jul 18, 2025):

It's very welcome to submit PRs, as always, then 2 approvals from maintainers can merge the PR, so the PR's code needs to be reviewable/maintainable and have tests for large changes. Thank you very much! 🙏

@wxiaoguang commented on GitHub (Jul 18, 2025): It's very welcome to submit PRs, as always, then 2 approvals from maintainers can merge the PR, so the PR's code needs to be reviewable/maintainable and have tests for large changes. Thank you very much! 🙏
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13859