After the page was renamed, we need to narrow links leading to Gerrit/Getting started. Either to Gerrit/Tutorial/tl;dr or to Gerrit/Tutorial, it depends on the context for every link. It is pretty simple to narrow them here on mwwiki, but it will be harder to narrow links from content wikis, wikitech, meta, etc. So any help appreciated!
Anyone willing to help with narrowing links?
Global git-review configuration deprecated
Under git-review 1.25.0, I'm now getting a "Using global/system git-review config files (.config/git-review/git-review.conf) is deprecated" with each review push. What's the best solution? Move defaultremote=origin into each repo's .gitreview file, a la https://gerrit.wikimedia.org/r/224872?
Have you got multiple remotes, where some are ssh and some aren't ?
This comes a bit late but in case it might help someone, the Tutorial#Configuring_git-review section has been updated to reference the new way. Just run this command instead of using the file:
git config --global gitreview.remote origin
Hello, I propose to move this page to a better name. The name is a little bit confusing as novice users usually expect "getting started" to be a good novice tutorial. But for this purpose we have got /Tutorial page. And on this page are more likely an instructions for at least a little experienced users, some tl;dr of /Tutorial for those, who know, what to do, what these commands mean, just don't remember them, right?
I am not a good english speaker, so I don't know, how to say my suggested name in english, so I'll try to explain those czech words to english: something like "notes/lists of commands/methods usually used for working with Gerrit" (or something like "tl;dr" or "basic usage" or "short guide" or something)
https://phabricator.wikimedia.org/T161901 might be of interest.
Well, at least this Tutorial I used as a novice user and this Getting started I use now as an experienced user as perfect. I wish some similar approach would be created also for Toollabs.
Tried, was not successfull, that tutorial is not really well written :/
This is more like an intro than good novice tutorial and how-to guide. I tried to use Toolforge according to those tutorials unsuccessfully, but there is going to be some Toolforge workshop by Czech Wikimedia, so I'll learn to work with Toolforge there and then try to improve these tutorials to be usable for people like me: really technically based/knowledged/experienced people, who don't understand manuals provided and who would really use the service if know how to. But off-topic
I created this page in 2012 when MediaWiki was transitioning from SVN to Git. Back then, a lot of people, including myself, were not familiar with Git, and even fewer people were familiar with Gerrit. The page "Gerrit/Workflow" was written, but people complained that it's too long, because it was about 20 pages in print (since then it was quite appropriately renamed to Gerrit/Advanced usage). So somebody wrote Gerrit/Tutorial, with the purpose of being a simpler page. Unfortunately, that page also quickly grew to about 20 pages in print.
So I created this page with the intention of being a very short Git manual, which would give the most basic and frequently-needed commands, and link to other pages for more advanced or rarely needed info. In the invisible HTML comment at the top I wrote that it must remain under one page in print. To match this purpose, I called it "Git/TLDR".
I don't know why was it renamed to "Gerrit/Getting started".
I'm biased, of course, but I support moving it back to "Git/TLDR".
I'm fine with
Moved, as it is mostly tl;dr of the Tutorial, I moved it as a subpage of it.
Install and configure Git
points to https://help.github.com/articles/set-up-git which suggests to Download GitHub for Windows but using this Windows-Client, is it possible to contribute to MediaWiki?
We (qa/browsertests) have at least one contributor working on Windows. Why do you think that would not be possible?
@Zeljko.filipin: He's asking specifically whether it is possible to contribute to MediaWiki repositories (which are hosted with Gerrit) from the GUI app "GitHub for Windows" (not general Git command-line for Windows). It's understandable that that app might not be capable of interacting with non-GitHub repositories, though afaik that works fine. Note though most manuals all assume git command line, so even if it would work, you may want to stick with that for having lots of plugins and documentation to choose from (and other people who can help).
@Krinkle: thanks for the explanation.
I was pairing (remotely) with our OPW intern Rachel recently and she made a commit from Github for Windows app. As far as I remember the app did not add Change-Id to the commit message so Gerrit complained when she tried to push code there. Github for Windows is easy to install and has a good diff tool, but I would not recommend it for committing. The app will create Git Shell shortcut on desktop during the installation. I would recommend using Git Shell for committing.
Yuvipanda suggested committing to GitHub and G2G would care about the remaining parts. This seems to be convenient to me. (Currently I am using Linux VMs, that also worked fine but they always take ages to load).
importance of scp
This post by Qgil-WMF was moved on 2013-03-02. You can find it at Thread:Talk:Gerrit/Getting started/importance of scp.