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

[FR] Displaying of hex colors #1306

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

Originally created by @gsantner on GitHub (Dec 1, 2017).

  • Gitea version (or commit ref): v1.3.0

Description

GitHub added displaying of hex colors in rendered markdown some time ago, I just noticted it today. have to admit, to like it very much and find it useful, so suggesting it for gitea too. See screenshot below how it is visualized, or the referenced issue. I usually paste them in some color viewer, or guess colors, but having them directly shown is a really nice idea.

https://github.com/gsantner/markor/issues/144

screenshot_2017-12-01__14-33_3

Originally created by @gsantner on GitHub (Dec 1, 2017). - Gitea version (or commit ref): v1.3.0 ## Description GitHub added displaying of hex colors in rendered markdown some time ago, I just noticted it today. have to admit, to like it very much and find it useful, so suggesting it for gitea too. See screenshot below how it is visualized, or the referenced issue. I usually paste them in some color viewer, or guess colors, but having them directly shown is a really nice idea. <https://github.com/gsantner/markor/issues/144> ![screenshot_2017-12-01__14-33_3](https://user-images.githubusercontent.com/6735650/33484900-ab556440-d6a4-11e7-99b6-16f0cfaa5144.png)
GiteaMirror added the issue/confirmedtype/feature labels 2025-11-02 03:56:11 -06:00
GiteaMirror commented 2025-11-02 03:56:12 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 10, 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 10, 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:56:12 -06:00
Author
Owner
Copy Link

@sglux commented on GitHub (Aug 19, 2021):

Yes, indeed, this would be nice to have.
@lunny what does the label you added mean? It is since 2017 on milestone 1.x.x and we have 1.14.6 right now ;-)

@sglux commented on GitHub (Aug 19, 2021): Yes, indeed, this would be nice to have. @lunny what does the label you added mean? It is since 2017 on milestone 1.x.x and we have 1.14.6 right now ;-)
GiteaMirror commented 2025-11-02 03:56:12 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 19, 2021):

That label will prevent stale bot mark it as stale. That means I think the issue should not be closed directly.

@lunny commented on GitHub (Aug 19, 2021): That label will prevent stale bot mark it as stale. That means I think the issue should not be closed directly.
GiteaMirror commented 2025-11-02 03:56:12 -06:00
Author
Owner
Copy Link

@gsantner commented on GitHub (Sep 8, 2021):

this is how it looks nowadays on github:

grafik

@gsantner commented on GitHub (Sep 8, 2021): this is how it looks nowadays on github: ![grafik](https://user-images.githubusercontent.com/6735650/132580350-b13bf9d2-d59d-4fe0-b91b-481cc25418b5.png)
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 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#1306
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?