github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-10 22:06:34 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Logo files name #4354

New Issue
Closed
opened 2025-11-02 05:47:50 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 05:47:50 -06:00
Owner
Copy Link

Originally created by @emilekm on GitHub (Nov 19, 2019).

The logo files are named gitea-{sm,lg}.png. If you're trying to substitute them with your own files then your logo name will become gitea[...].png which would mean that the logo represents Gitea and not the actual brand.

Proposition:
The "gitea" part of the name should be substituted with "logo" (logo-{sm,lg}.png).
Also "sm/lg" hints that there might be a version of the file without this suffix (medium) and maybe it would be good to use it instead of "lg".

I can prepare PR when this is accepted.

Originally created by @emilekm on GitHub (Nov 19, 2019). The logo files are named `gitea-{sm,lg}.png`. If you're trying to substitute them with your own files then your logo name will become `gitea[...].png` which would mean that the logo represents Gitea and not the actual brand. Proposition: The "gitea" part of the name should be substituted with "logo" (`logo-{sm,lg}.png`). Also "sm/lg" hints that there might be a version of the file without this suffix (medium) and maybe it would be good to use it instead of "lg". I can prepare PR when this is accepted.
GiteaMirror added the pr/breakingissue/staleissue/needs-feedback labels 2025-11-02 05:47:50 -06:00
GiteaMirror commented 2025-11-02 05:47:52 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 19, 2019):

This would break backward compatibility and it is not user visible anyway so I don't see much point in that keeping in mind about backward compatibility

@lafriks commented on GitHub (Nov 19, 2019): This would break backward compatibility and it is not user visible anyway so I don't see much point in that keeping in mind about backward compatibility
GiteaMirror commented 2025-11-02 05:47:52 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 19, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 19, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
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 issue/needs-feedback issue/stale pr/breaking
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#4354
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?