6,608
edits
Template talk:Repo link: Difference between revisions
→topic/foo branch specification ?
(→topic/foo branch specification ?: new section) |
|||
| Line 179: | Line 179: | ||
Referring to [http://wiki.flightgear.org/index.php?title=Hackathon_Proposal:_CompositeViewer_and_Canvas&oldid=129050] Why is this needed ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 13:53, 16 November 2020 (EST) | Referring to [http://wiki.flightgear.org/index.php?title=Hackathon_Proposal:_CompositeViewer_and_Canvas&oldid=129050] Why is this needed ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 13:53, 16 November 2020 (EST) | ||
: Wow, that's stretching my memory. I guess you mean the <code>/~</code> needed at the end of SourceForge branches. I think that I was going to implement the proper URL construction with <code>/~</code>, but the logic required evaded me and I never completed it. The problem is documented in {{tl|repo link}}, specifically in the parameter help description. E.g.: | |||
: <q>For SourceForge git repositories, if the character <code>/</code> is present in the branch name, the text <code>/~</code> must be appended to the branch.</q> | |||
: I'm not sure if MediaWiki allows us to detect if a certain character is present in a template parameter value. Again from distant memory, I think I asked for an extension to be installed to enable this to be implemented, but it never was. This is not a simple problem! Hence I took the shortcut of using the above text in the documentation. | |||
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 16:19, 16 November 2020 (EST) | |||