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

Repository logo #247

New Issue
Closed
opened 2025-11-02 03:15:43 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-02 03:15:43 -06:00
Owner
Copy Link

Originally created by @DeltaEvo on GitHub (Jan 18, 2017).

  • Gitea version (or commit ref): all
  • Git version: all
  • Operating system: all
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When I use gitlab, I use the logo to recognize the repo that I was looking for. Like Gitlab and Bitbucket i would be nice to provide the ability to add logo to repositories

Originally created by @DeltaEvo on GitHub (Jan 18, 2017). - Gitea version (or commit ref): all - Git version: all - Operating system: all - Database (use `[x]`): - [x] PostgreSQL - [x] MySQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description When I use gitlab, I use the logo to recognize the repo that I was looking for. Like Gitlab and Bitbucket i would be nice to provide the ability to add logo to repositories
GiteaMirror added the topic/uiissue/confirmedtype/feature labels 2025-11-02 03:15:43 -06:00
GiteaMirror commented 2025-11-02 03:15:44 -06:00
Author
Owner
Copy Link

@lofidevops commented on GitHub (Apr 27, 2017):

On GitLab and Bitbucket this is implemented by uploading an image to the code host. It would be convenient if you could instead/also point to an image file in the repo itself (presumably on the master branch). This way, if that file is changed, the logo changes too.

@lofidevops commented on GitHub (Apr 27, 2017): On GitLab and Bitbucket this is implemented by uploading an image to the code host. It would be convenient if you could instead/also point to an image file in the repo itself (presumably on the master branch). This way, if that file is changed, the logo changes too.
GiteaMirror commented 2025-11-02 03:15:44 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 27, 2017):

@kwill It seems interesting to get the logo file from the repo.

@lunny commented on GitHub (Apr 27, 2017): @kwill It seems interesting to get the logo file from the repo.
GiteaMirror commented 2025-11-02 03:15:45 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 12, 2019):

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 (Feb 12, 2019): 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.
GiteaMirror commented 2025-11-02 03:15:45 -06:00
Author
Owner
Copy Link

@NotAFile commented on GitHub (Feb 12, 2019):

this issue is not stale (maybe stalebot should be disabled for feature requests?)

@NotAFile commented on GitHub (Feb 12, 2019): this issue is not stale (maybe stalebot should be disabled for feature requests?)
GiteaMirror commented 2025-11-02 03:15:45 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 6, 2019):

I think @sergey-dryabzhinsky would like to send a PR to resolve this issue.

@lunny commented on GitHub (May 6, 2019): I think @sergey-dryabzhinsky would like to send a PR to resolve this issue.
GiteaMirror commented 2025-11-02 03:15:45 -06:00
Author
Owner
Copy Link

@sergey-dryabzhinsky commented on GitHub (May 19, 2019):

First version of patch in #6986 ready for review

@sergey-dryabzhinsky commented on GitHub (May 19, 2019): First version of patch in #6986 ready for review
GiteaMirror commented 2025-11-02 03:15:45 -06:00
Author
Owner
Copy Link

@sergey-dryabzhinsky commented on GitHub (May 19, 2019):

How it looks:

Repository list
Снимок экрана_2019-05-19_05-48-00

Repository page
Снимок экрана_2019-05-19_05-49-02

Repository settings
Снимок экрана_2019-05-19_05-49-43

@sergey-dryabzhinsky commented on GitHub (May 19, 2019): How it looks: Repository list ![Снимок экрана_2019-05-19_05-48-00](https://user-images.githubusercontent.com/717597/57977118-c165c280-79f9-11e9-8395-9abc4b20374b.png) Repository page ![Снимок экрана_2019-05-19_05-49-02](https://user-images.githubusercontent.com/717597/57977119-d2aecf00-79f9-11e9-97d9-90dd516652f3.png) Repository settings ![Снимок экрана_2019-05-19_05-49-43](https://user-images.githubusercontent.com/717597/57977120-eeb27080-79f9-11e9-9a93-6e6574eb6b2b.png)
GiteaMirror commented 2025-11-02 03:15:46 -06:00
Author
Owner
Copy Link

@Mikanoshi commented on GitHub (May 20, 2019):

I think project list should be like this

projects_small

or this

projects_large

And project view like this

view_small

or even this (where's the search? no idea :D)

view_large

@Mikanoshi commented on GitHub (May 20, 2019): I think project list should be like this ![projects_small](https://user-images.githubusercontent.com/5113439/58031326-997d7880-7b39-11e9-9e26-c975257c2f9b.png) or this ![projects_large](https://user-images.githubusercontent.com/5113439/58031338-9e422c80-7b39-11e9-8e2d-61e1e456af64.png) And project view like this ![view_small](https://user-images.githubusercontent.com/5113439/58031349-a7cb9480-7b39-11e9-839e-9edefa080bf9.png) or even this (where's the search? no idea :D) ![view_large](https://user-images.githubusercontent.com/5113439/58031352-ab5f1b80-7b39-11e9-8d76-f4ed8203e957.png)
GiteaMirror commented 2025-11-02 03:15:46 -06:00
Author
Owner
Copy Link

@sergey-dryabzhinsky commented on GitHub (May 20, 2019):

Updated to:

project list
Снимок экрана_2019-05-21_02-01-54

project view
Снимок экрана_2019-05-21_02-02-46

@sergey-dryabzhinsky commented on GitHub (May 20, 2019): Updated to: project list ![Снимок экрана_2019-05-21_02-01-54](https://user-images.githubusercontent.com/717597/58057135-7a4c0e80-7b6c-11e9-9f45-3f59a494ecde.png) project view ![Снимок экрана_2019-05-21_02-02-46](https://user-images.githubusercontent.com/717597/58057170-95b71980-7b6c-11e9-8c9a-7b40d9e72ced.png)
GiteaMirror commented 2025-11-02 03:15:46 -06:00
Author
Owner
Copy Link

@sergey-dryabzhinsky commented on GitHub (May 20, 2019):

Not empty project
Снимок экрана_2019-05-21_02-05-22

@sergey-dryabzhinsky commented on GitHub (May 20, 2019): Not empty project ![Снимок экрана_2019-05-21_02-05-22](https://user-images.githubusercontent.com/717597/58057242-ec245800-7b6c-11e9-9ddd-de8050940ab2.png)
GiteaMirror commented 2025-11-02 03:15:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 21, 2019):

I like @Mikanoshi 's first one repositories list.

@lunny commented on GitHub (May 21, 2019): I like @Mikanoshi 's first one repositories list.
GiteaMirror commented 2025-11-02 03:15:47 -06:00
Author
Owner
Copy Link

@sergey-dryabzhinsky commented on GitHub (May 21, 2019):

@lunny Like that?
Снимок экрана_2019-05-21_17-39-05

@sergey-dryabzhinsky commented on GitHub (May 21, 2019): @lunny Like that? ![Снимок экрана_2019-05-21_17-39-05](https://user-images.githubusercontent.com/717597/58105574-6695bc00-7bef-11e9-875a-b4e98e32a8fb.png)
GiteaMirror commented 2025-11-02 03:15:47 -06:00
Author
Owner
Copy Link

@sergey-dryabzhinsky commented on GitHub (May 30, 2019):

#6986 merged into master
Will be in 1.9.0 release

@sergey-dryabzhinsky commented on GitHub (May 30, 2019): #6986 merged into master Will be in 1.9.0 release
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/confirmed topic/ui type/feature
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#247
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?