Feature Request | Markdown Link as GitHub does #1621

New Issue

GiteaMirror · 2025-11-02T04:07:00-06:00

GiteaMirror commented

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

Originally created by @alexandrestein on GitHub (Mar 13, 2018).

Description

It can be useful to know how to deal with the markdown.
I trued to make the changes on my own but I got too many errors and the software is really heavy.
Sorry...

It would only be a template update to have some thing similar to GitHub with the link Styling with Markdown is supported.
But in our case the link would point to daring fireball.

Screenshots

Originally created by @alexandrestein on GitHub (Mar 13, 2018).  ## Description It can be useful to know how to deal with the markdown. I trued to make the changes on my own but I got too many errors and the software is really heavy. Sorry... It would only be a template update to have some thing similar to `GitHub` with the link `Styling with Markdown is supported`. But in our case the link would point to [daring fireball](https://daringfireball.net/projects/markdown/syntax). ## Screenshots ![capture d ecran de 2018-03-13 15-36-31](https://user-images.githubusercontent.com/5431025/37349294-5f9b236e-26d6-11e8-8cb1-aec99c051a4d.png)

GiteaMirror added the topic/ui type/enhancement issue/stale labels 2025-11-02 04:07:00 -06:00

GiteaMirror closed this issue

2025-11-02 04:07:01 -06:00

GiteaMirror commented

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

@jonasfranz commented on GitHub (Mar 17, 2018):

I think that an external link is not a good idea.

@jonasfranz commented on GitHub (Mar 17, 2018): I think that an external link is not a good idea.

GiteaMirror commented

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

@alexandrestein commented on GitHub (Mar 17, 2018):

That's right.
An new page inside Gitea would probably be better.

Some kind of clone from the page a gave earlier should be fine.
For what I see there is no license issue.

@alexandrestein commented on GitHub (Mar 17, 2018): That's right. An new page inside `Gitea` would probably be better. Some kind of clone from the page a gave earlier should be fine. For what I see there is no license issue.

GiteaMirror commented

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

@jonasfranz commented on GitHub (Mar 17, 2018):

@alexandreStein You could add it to the docs at docs.gitea.io by creating a PR. I do not see any license information at the page itself. Do you know which license it is?

@jonasfranz commented on GitHub (Mar 17, 2018): @alexandreStein You could add it to the docs at docs.gitea.io by creating a PR. I do not see any license information at the page itself. Do you know which license it is?

GiteaMirror commented

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

@alexandrestein commented on GitHub (Mar 18, 2018):

Sorry.
You are right about the license.
The package is under BSD but there is nothing on the syntax page itself.
And I didn't found any syntax documentation in the source as well.

I'm not a licensing expert.
Does this mean that the page needs to be rewrite?

@alexandrestein commented on GitHub (Mar 18, 2018): Sorry. You are right about the license. The package is under BSD but there is nothing on the syntax page itself. And I didn't found any syntax documentation in the source as well. I'm not a licensing expert. Does this mean that the page needs to be rewrite?

GiteaMirror commented

2025-11-02 04:07:03 -06:00

@stale[bot] commented on GitHub (Feb 4, 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 4, 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 04:07:03 -06:00

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

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 18, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 11:58:51 -06:00

[PR #1621] [MERGED] fix lost text color on button on set as primary email #15954

Sign in to join this conversation.