enhance(repo): add custom name (display name) to repositories - #39208
Draft
oierxjn wants to merge 7 commits into
Draft
enhance(repo): add custom name (display name) to repositories#39208oierxjn wants to merge 7 commits into
oierxjn wants to merge 7 commits into
Conversation
Add an optional Unicode-friendly display name decoupled from the ASCII repository name used in URLs, git and SSH paths. DisplayName() falls back to the repository name when unset, so existing repositories render unchanged. Assisted-by: deepseek-v4-flash
Allow setting the custom name on repository create/edit and include it in repository payloads. Regenerated the swagger spec. Assisted-by: deepseek-v4-flash
Add the custom name input to the create-repository form and the basic settings form, wired through the existing form handlers. Assisted-by: deepseek-v4-flash
Show DisplayName() in the repository header, the shared repo list (used by explore, profile, org home, forks and more), settings and admin lists, and page/og meta titles. The raw repository name is kept as a tooltip and remains the search identity. Repo search now also matches the custom name. Assisted-by: deepseek-v4-flash
GiteaBot
added
the
lgtm/need 2
Author
|
Draft for review. Branch base is upstream main; if maintainers prefer a different field name (e.g. display_name) or a narrower UI scope, the branch will be updated with new commits. Authored with assistance from deepseek-v4-flash. |
checks-backend's openapi3-check failed because only the Swagger 2.0 spec was regenerated; the OpenAPI 3.0 spec is derived from it. Assisted-by: deepseek-v4-flash
Address Copilot review: the always-on keyword match against custom_name had no test coverage. Extend TestSearchRepository with a Unicode custom name fixture case, mirroring the existing description keyword tests. Assisted-by: deepseek-v4-flash
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an optional, Unicode-friendly display name (custom name) for repositories, decoupled from the ASCII path name used in URLs, git and SSH. When unset, everything renders exactly as before.
Usage: repository owners set "Custom name" on the repo settings page (or via
custom_namein the create/edit API). It is shown in the repo header, repo lists, settings/admin lists and page/og meta; URLs, git and SSH keep using the repository name, and the path name stays available as a tooltip. Repo search also matches the custom name.Testing: a unit test covers the DisplayName() fallback logic; create/edit API plumbing reuses the existing handlers; templates pass the repo's djlint profile. Screenshots will be added once the UI can be run locally (draft).
Implements the long-standing human-readable project name request: #9032