Codeberg/Community
54
325
Fork
You've already forked Community
12

URL in repo description loses underscore #330

Closed
opened 2020年11月02日 13:33:50 +01:00 by jolson · 18 comments

One of my repositories has the following description text:

Anteckningar från Frederic P. Schullers föreläsningar i allmän relativitetsteori https://www.youtube.com/playlist?list=PLFeEvEPtX_0S6vxxiiNPrJbLu9aK1UVC_

When the URL is rendered into a link, the underscore is left out, so that the link leads to a non-existing page

As per RFC 3986, I have tried delimiting the URL with quotation marks, which change nothing, and with < and >, which makes the URL disappear.

One of my [repositories](https://codeberg.org/jolson/relativitetsanteckningar) has the following description text: `Anteckningar från Frederic P. Schullers föreläsningar i allmän relativitetsteori https://www.youtube.com/playlist?list=PLFeEvEPtX_0S6vxxiiNPrJbLu9aK1UVC_` When the URL is rendered into a link, the underscore is left out, so that the link leads to a non-existing page As per [RFC 3986](https://tools.ietf.org/html/rfc3986#appendix-C), I have tried delimiting the URL with quotation marks, which change nothing, and with `<` and `>`, which makes the URL disappear.

Odd behavior, text enclosed in angle brackets <> in repo descriptions don't render. Hyperlinks also don't work in the repo description. Perhaps this is intended, since there is also a repo setting for a website.

Odd behavior, text enclosed in angle brackets `<>` in repo descriptions don't render. Hyperlinks also don't work in the repo description. Perhaps this is intended, since there is also a repo setting for a website.
Author
Copy link

When the URL is rendered into a link, the underscore is left out

Only the trailing underscore. I just realised that there is another underscore in the URL, and that one is included correctly.

> When the URL is rendered into a link, the underscore is left out Only the trailing underscore. I just realised that there is another underscore in the URL, and that one is included correctly.

can you create an issue upstream or should I do?

can you create an issue upstream or should I do?
Author
Copy link

can you create an issue upstream or should I do?

Please do! I didn't know if this concerned Gitea in general or just Codeberg, and I didn't have another Gitea instance on which to try it.

> can you create an issue upstream or should I do? Please do! I didn't know if this concerned Gitea in general or just Codeberg, and I didn't have another Gitea instance on which to try it.

can you create an issue upstream or should I do?

Please do! I didn't know if this concerned Gitea in general or just Codeberg, and I didn't have another Gitea instance on which to try it.

@jolson It's in gh now

https://github.com/go-gitea/gitea

> > can you create an issue upstream or should I do? > > Please do! I didn't know if this concerned Gitea in general or just Codeberg, and I didn't have another Gitea instance on which to try it. @jolson It's in gh now https://github.com/go-gitea/gitea
Author
Copy link

@jolson It's in gh now

https://github.com/go-gitea/gitea

Filed as an issue, you mean? I can't find it. Do you think you could link to it?

> @jolson It's in gh now > > https://github.com/go-gitea/gitea Filed as an issue, you mean? I can't find it. Do you think you could link to it?

Maybe can use markdown render do it.

Maybe can use markdown render do it.
Author
Copy link

Maybe can use markdown render do it.

Good idea. It apparently does not render it as Markdown. See attached screenshot.

> Maybe can use markdown render do it. Good idea. It apparently does not render it as Markdown. See attached screenshot.

@a1012112796 repository description do not support markdown - but this would solve it

@a1012112796 repository description do not support markdown - but this would solve it
upstream issue: https://github.com/go-gitea/gitea/issues/13404
@jolson fixed upstream (demo: https://try.gitea.io/abcKing/noReaction)
Author
Copy link

@6543

@jolson fixed upstream (demo: https://try.gitea.io/abcKing/noReaction)

I guess it is a Codeberg issue now! :-)

It's nice to know about <try.gitea.io>, which I presume is kept updated with the latest builds.

Edit: Enclosing between < and > still makes the URL not show at all.

@6543 > @jolson fixed upstream (demo: https://try.gitea.io/abcKing/noReaction) I guess it _is_ a Codeberg issue now! :-) It's nice to know about <try.gitea.io>, which I presume is kept updated with the latest builds. Edit: Enclosing between `<` and `>` still makes the URL not show at all.
Member
Copy link

@6543

@jolson fixed upstream (demo: https://try.gitea.io/abcKing/noReaction)

I guess it is a Codeberg issue now! :-)

hehe, will get deployed with next batch of updates

> @6543 > > @jolson fixed upstream (demo: https://try.gitea.io/abcKing/noReaction) > > I guess it _is_ a Codeberg issue now! :-) hehe, will get deployed with next batch of updates
@hw if you like ... https://github.com/go-gitea/gitea/pull/13408

@6543

Cool, thanks! This is deployed since yesterday evening :)

@jolson

I looked at your repo, seems fixed, so closing. Thanks for reporting 👍

@6543 Cool, thanks! This is deployed since yesterday evening :) @jolson I looked at your repo, seems fixed, so closing. Thanks for reporting 👍
Author
Copy link

@ashimokawa

I looked at your repo, seems fixed, so closing. Thanks for reporting 👍

Thank you! It has been a pleasant experience.

The only tricky thing was figuring out that "Community" is the place where you report issues about the Codeberg website.

@ashimokawa > I looked at your repo, seems fixed, so closing. Thanks for reporting 👍 Thank you! It has been a pleasant experience. The only tricky thing was figuring out that "Community" is the place where you report issues about the Codeberg website.

@jolson
Hmmm... in the top bar there is a link which says "Codeberg Issues" which links here.

@jolson Hmmm... in the top bar there is a link which says "Codeberg Issues" which links here.
Author
Copy link

@ashimokawa

Hmmm... in the top bar there is a link which says "Codeberg Issues" which links here.

You are right. I guess the name Community gave me other associations, making me think that I perhaps had come to the wrong place after all. I thought it was a discussion forum or something like that.

@ashimokawa > Hmmm... in the top bar there is a link which says "Codeberg Issues" which links here. You are right. I guess the name _Community_ gave me other associations, making me think that I perhaps had come to the wrong place after all. I thought it was a discussion forum or something like that.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#330
Reference in a new issue
Codeberg/Community
No description provided.
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?