Add quoting mechanism directly from source files pages. #5328

New Issue

GiteaMirror · 2025-11-02T06:21:43-06:00

GiteaMirror commented

2025-11-02 06:21:43 -06:00

Originally created by @kevung on GitHub (Apr 30, 2020).

Hello Gitea community.

I would like to quote source file lines directly in issues (and outside any pull request mechanism), as it is possible to do so on Github:

Here is such an example:

Originally posted by @guillep2k in https://github.com/go-gitea/gitea/issues/7818#issuecomment-540835972

For the moment, to do so on Gitea, one has to click on line numbers (on the left side of the source file content) and copy-paste the Url (http://mygiteaserver/user/myrepot/src/branch/master/examplefile.txt#LX where X is the number of the line to be reffered to) into the issue where the discussion takes place.

It would be very nice to be able to open a new issue directly by clicking on the line number as in Github.

Regards,

Originally created by @kevung on GitHub (Apr 30, 2020). Hello Gitea community. I would like to quote source file lines directly in issues (and outside any pull request mechanism), as it is possible to do so on Github: Here is such an example: ![image](https://user-images.githubusercontent.com/18600385/66613054-7e6bdd80-eb9a-11e9-9f5d-57d42ae5cd3a.png) _Originally posted by @guillep2k in https://github.com/go-gitea/gitea/issues/7818#issuecomment-540835972_ For the moment, to do so on Gitea, one has to click on line numbers (on the left side of the source file content) and copy-paste the Url (http://mygiteaserver/user/myrepot/src/branch/master/examplefile.txt#LX where X is the number of the line to be reffered to) into the issue where the discussion takes place. It would be very nice to be able to open a new issue directly by clicking on the line number as in Github. Regards,

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 06:21:43 -06:00

GiteaMirror commented

2025-11-02 06:21:44 -06:00

@stale[bot] commented on GitHub (Jul 1, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 1, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:21:44 -06:00

@wxiaoguang commented on GitHub (Apr 15, 2025):

We partially have it in 1.23. Two steps: copy permlink, and create an new issue, then the code block will be rendered in the issue.

The "Reference in new issue" seems not difficult to support .... 😄

@wxiaoguang commented on GitHub (Apr 15, 2025): We partially have it in 1.23. Two steps: copy permlink, and create an new issue, then the code block will be rendered in the issue. ---- The "Reference in new issue" seems not difficult to support .... 😄

GiteaMirror referenced this issue

2025-11-02 16:01:20 -06:00

[PR #5511] [MERGED] Fixing MSSQL timestamp type #17820

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#5328