20,741
edits
Template talk:Repo link: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→needs to be updated for different protocols: Ah, so Template:Repo link should be used as a meta template for more specific link templates for individual repos?) |
No edit summary |
||
| Line 19: | Line 19: | ||
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:10, 5 April 2015 (EDT) | ::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:10, 5 April 2015 (EDT) | ||
:: correct, I am basically thinking along the lines of using/generalizing existing templates to generalize our "hard-coded" (for the lack of a better term) repository URLs in pretty much all wiki articles - so that updating repository URLs in the future will be mainly a matter of changing 2-3 templates. Which is why I suggested to also add support for different protocols, so that those templates can also be used for instructions on cloning/pulling using non-default (non-http) protocols. This would also allow us to introduce meta templates for document clone/update/pull instructions using a single template for different front-ends - possibly even including annotated screen shots. We kinda started preparing this a while ago by introducing templates like these: | |||
:: * http://wiki.flightgear.org/Template:Git_clone | |||
:: * http://wiki.flightgear.org/Template:Git_checkout | |||
:: * http://wiki.flightgear.org/Template:Git_push | |||
:: Once we adapt the new repo link template, we could easily use that for also maintaining everything easily. And the corresponding clone/checkout/push and pull templates could also contain instructions for different front-ends (think git command line vs. TortoiseGit), to help generalize our docs, especially for people on Windows/Mac OSX not as familiar with CLI environments.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:59, 5 April 2015 (EDT) | |||