Allow Ctrl+V to paste new images into Wiki #7934

New Issue

GiteaMirror · 2025-11-02T07:42:09-06:00

GiteaMirror commented

2025-11-02 07:42:09 -06:00

Originally created by @mappu on GitHub (Oct 5, 2021).

Feature Description

When editing an issue comment, you can paste in new image attachments. It's a great low-friction way to make an issue more understandable, especially for screenshots.

It would be great to have this same capability to add images to Wiki documents.

Right now, you can only either (A) clone the git repo and add them manually, which is difficult for non-developer staff; or (B) create a dummy-issue for image uploads and copy the links into the wiki, which is a strange workaround

Screenshots

No response

Originally created by @mappu on GitHub (Oct 5, 2021). ### Feature Description When editing an issue comment, you can paste in new image attachments. It's a great low-friction way to make an issue more understandable, especially for screenshots. It would be great to have this same capability to add images to Wiki documents. Right now, you can only either (A) clone the git repo and add them manually, which is difficult for non-developer staff; or (B) create a dummy-issue for image uploads and copy the links into the wiki, which is a strange workaround ### Screenshots _No response_

GiteaMirror added the topic/wiki topic/ui-interaction labels 2025-11-02 07:42:09 -06:00

GiteaMirror closed this issue

2025-11-02 07:42:09 -06:00

GiteaMirror commented

2025-11-02 07:42:10 -06:00

@noerw commented on GitHub (Oct 8, 2021):

The underlying issue is, that images on issues and comments are stored in an attachment storage backend (local filesystem, s3, ...), and the data model for attachments currently does not support linking an attachment to a wiki page, so the logic of simple file uploads can not be trivially ported to the wiki.

This should be easy to extend, though we should consider whether it is good design to have images of the wiki stored externally to the wiki git repo, as it won't be selfcontained anymore.

@noerw commented on GitHub (Oct 8, 2021): The underlying issue is, that images on issues and comments are stored in an attachment storage backend (local filesystem, s3, ...), and the [data model for attachments](https://github.com/go-gitea/gitea/blob/1c3ae6d05e6099d30f61a9057d8e12cdfc80975d/models/attachment.go#L21-L34) currently does not support linking an attachment to a wiki page, so the logic of simple file uploads can not be trivially ported to the wiki. This should be easy to extend, though we should consider whether it is good design to have images of the wiki stored externally to the wiki git repo, as it won't be selfcontained anymore.

GiteaMirror commented

2025-11-02 07:42:10 -06:00

@wupei1024 commented on GitHub (Apr 21, 2022):

The underlying issue is, that images on issues and comments are stored in an attachment storage backend (local filesystem, s3, ...), and the data model for attachments currently does not support linking an attachment to a wiki page, so the logic of simple file uploads can not be trivially ported to the wiki.

This should be easy to extend, though we should consider whether it is good design to have images of the wiki stored externally to the wiki git repo, as it won't be selfcontained anymore.

to upload attachments with md file to same reposistory is useful.
pull all file to localhost and compile .md & images to html website

@wupei1024 commented on GitHub (Apr 21, 2022): > The underlying issue is, that images on issues and comments are stored in an attachment storage backend (local filesystem, s3, ...), and the [data model for attachments](https://github.com/go-gitea/gitea/blob/1c3ae6d05e6099d30f61a9057d8e12cdfc80975d/models/attachment.go#L21-L34) currently does not support linking an attachment to a wiki page, so the logic of simple file uploads can not be trivially ported to the wiki. > > This should be easy to extend, though we should consider whether it is good design to have images of the wiki stored externally to the wiki git repo, as it won't be selfcontained anymore. to upload attachments with md file to same reposistory is useful. pull all file to localhost and compile .md & images to html website

GiteaMirror commented

2025-11-02 07:42:10 -06:00

@KiaraGrouwstra commented on GitHub (Dec 19, 2022):

the wikis are just git repos, right? couldn't they store image files?

@KiaraGrouwstra commented on GitHub (Dec 19, 2022): the wikis are just git repos, right? couldn't they store image files?

GiteaMirror commented

2025-11-02 07:42:10 -06:00

@ivptr commented on GitHub (Dec 22, 2022):

Yes, wikis are Git repos: https://github.com/go-gitea/gitea/issues/1426#issuecomment-290888504

The whole idea is to allow non-tech staff to edit documentation in Wiki, add screenshots, other attachments etc.

Currently this is not possible because images need to be committed to main repository first and then its path referenced in Wiki.

This is related to #574.

@ivptr commented on GitHub (Dec 22, 2022): Yes, wikis are Git repos: https://github.com/go-gitea/gitea/issues/1426#issuecomment-290888504 The whole idea is to allow non-tech staff to edit documentation in Wiki, add screenshots, other attachments etc. Currently this is not possible because images need to be committed to main repository first and then its path referenced in Wiki. This is related to #574.

GiteaMirror commented

2025-11-02 07:42:11 -06:00

@wxiaoguang commented on GitHub (Apr 25, 2023):

It's duplicate of https://github.com/go-gitea/gitea/issues/574, as long as #574 could be done, there is no problem for Ctrl+V

@wxiaoguang commented on GitHub (Apr 25, 2023): It's duplicate of https://github.com/go-gitea/gitea/issues/574, as long as #574 could be done, there is no problem for Ctrl+V

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#7934