Skip to content

GitLab

Switch branch/tag
  1. 08 Mar, 2019 7 commits
  3. 07 Mar, 2019 4 commits
    • techknowlogick's avatar
      Add robots.txt as reserved username (#6272) · 9fd8b262
      techknowlogick authored 
      Fix #6271
      Unverified
      9fd8b262
    • mrsdizzie's avatar
      Replace linkRegex with xurls library (#6261) · f2de5dc8
      mrsdizzie authored 
      * Replace linkRegex with xurls library

Rather than maintaining a complicated regex to match URLs for
autolinking, gitea can use this existing go library that takes care of
the matching with very little code change to gitea itself. After
spending a while trying to find the perfect regex for all cases this library
still works better as it is more flexible than a single regex ever will be.

This will also fix the following issues: #5844 #3095 #3381

This passes all our current tests and I've added new ones mentioned in
those issues as well.

* Use xurls.StrictMatchingScheme instead of xurls.Strict

This is much faster and we only care about https? links to preserve
existing behavior.
      f2de5dc8
    • GiteaBot's avatar
      [skip ci] Updated translations via Crowdin · 01bd1fcd
      GiteaBot authored
      01bd1fcd
    • mrsdizzie's avatar
      Remove visitLinksForShortLinks features (#6257) · 020075e1
      mrsdizzie authored 
      The visitLinksForShortLinks feature would look inside of an <a> tag and
run shortLinkProcessorFull on any text, which attempts to create links
out of potential 'short links' like [[test]] [[link|example]] etc...
This makes no sense because you can't have nested links within an <a>
tag. Specifically, the html5 standard says <a> tags can't include
interactive content if they contain the href attribute:

 http://w3c.github.io/html/single-page.html#the-a-element

And also defines an <a> element with a href attribute as interactive:

 http://w3c.github.io/html/single-page.html#interactive-content

Therefore you can't really put a link inside of another link. In
practice none of this works anyways since browsers won't render it, it
would probably be broken if they tried, and it is causing a bug
(#4946). No current tests rely on this behavior either.

This removes the feature and also explicitly excludes the
current visitNodeForShortLinks from looking in <a> tags.
      020075e1
  5. 06 Mar, 2019 2 commits
  7. 05 Mar, 2019 6 commits
  9. 03 Mar, 2019 1 commit
  11. 02 Mar, 2019 2 commits
    • Martin Delille's avatar
      add create issue via email comparison (#6227) · 8e202e28
      Martin Delille authored
      8e202e28
    • James E. Blair's avatar
      Fix renames over redirects (#6216) · a5604b16
      James E. Blair authored 
      
In #6211, we started creating repo_redirects for ownership transfers,
however that opens an edge case where a user might perform the
following sequence:

rename org1/repo1 -> org1/repo2  (creates org1/repo1 redirect)
transfer org2/repo1 -> org1/repo1 (org1/repo1 redirect continues to exist)
rename org1/repo1 -> org1/repo3 (fails due to existing org1/repo1 redirect)

This change ensures that each time we rename or transfer a repo,
we delete any existing redirects at the target location.  This
already happens when a new repo is created.  By doing this we ensure
that we'll never have both a repo and a redirect at the same location.
Signed-off-by: default avatarJames E. Blair <jeblair@redhat.com>
      a5604b16
  13. 01 Mar, 2019 3 commits
  15. 28 Feb, 2019 7 commits
  17. 27 Feb, 2019 5 commits
  19. 26 Feb, 2019 3 commits