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

[UI] highlight CVEs and link them #10977

New Issue
Open
opened 2025-11-02 09:23:48 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 09:23:48 -06:00
Owner
Copy Link

Originally created by @6543 on GitHub (Jun 6, 2023).

the CVE-2023-32682 should look like "CVE-2023-32682" and link to https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32682 ... similar to what we do with issue-indexes

-> we should have to add it to the markdown renderer

Originally created by @6543 on GitHub (Jun 6, 2023). the `CVE-2023-32682` should look like "[CVE-2023-32682](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32682)" and link to https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32682 ... similar to what we do with issue-indexes -> we should have to add it to the markdown renderer
GiteaMirror added the type/featuretopic/ui labels 2025-11-02 09:23:48 -06:00
GiteaMirror commented 2025-11-02 09:23:48 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 6, 2023):

We should be linking to CVE.org instead of CVE.mitre.org

@techknowlogick commented on GitHub (Jun 6, 2023): We should be linking to CVE.org instead of CVE.mitre.org
GiteaMirror commented 2025-11-02 09:23:49 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Jun 6, 2023):

I guess this could be done as config and be general useful. Assuming ini can do this:

[markup.linkify]
CVE-[0-9-]+: https://www.cve.org/CVERecord?id=$1
JIRA-[0-9]+: https://jira.company.com/$1

Actual regex should include \b before and after to reduce false positives. It should also not replace inside code blocks.

@silverwind commented on GitHub (Jun 6, 2023): I guess this could be done as config and be general useful. Assuming ini can do this: ```ini [markup.linkify] CVE-[0-9-]+: https://www.cve.org/CVERecord?id=$1 JIRA-[0-9]+: https://jira.company.com/$1 ``` Actual regex should include `\b` before and after to reduce false positives. It should also not replace inside code blocks.
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 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#10977
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?