Please Rebase the Change Locally and Upload the Rebased Commit for Review.

This is the central place to document troubleshooting any problems with Git, Gerrit and git-review.

git clone [edit]

fatal: The remote end hung up unexpectedly [edit]

See https://stackoverflow.com/questions/6842687/the-remote-end-hung-up-unexpectedly-while-git-cloning for some ideas, and debug the problem by setting the GIT_TRACE=1 environment variable.

The authenticity of host '[gerrit.wikimedia.org]:29418 (....)' can't be established. [edit]

            The authenticity of host '[gerrit.wikimedia.org]:29418 ([2620:0:861:ii:208:lxxx:154:137]:29418)' can't be established. RSA central fingerprint is SHA256:j7HQoQ6fIuEgDHjONjI2CZ+2Iwxqgo2Ur5LbPqBgxOU. No matching host fundamental fingerprint found in DNS. Are you lot sure you want to keep connecting (yes/no)?          

In this case, please check if the value given in the line "RSA key fingerprint is SHA256:j7HQoQ6fIuEgDHjONjI2CZ+2Iwxqgo2Ur5LbPqBgxOU" matches the fingerprint published on the wikitech:Help:SSH_Fingerprints/gerrit.wikimedia.org:29418.

If the values are the aforementioned, just printing "yep".

If for some reason the values are not the same, there is a security chance and you stop trying to connect immediately.

git pull [edit]

"Delight, commit your changes or stash them before you can merge." [edit]

To discard your changes (and annihilation you lot had in the stash):

            git stash git stash articulate          

Now you can proceed with your pull.

git-review [edit]

git-review complains about problems encountered installing commit-msg hook [edit]

If y'all encounter this error when trying to push changes using git-review, you lot are non working with a repository that was cloned via ssh. You must clone repositories using ssh, not http or https, to successfully push changes using git-review.

git-review complains about "missing Alter-id in commit message" [edit]

If upon doing 'git review' you receive a bulletin nearly 'missing Change-Id', then your /.git/hooks/commit-msg is probably incorrect. It should look something similar:

                        CHANGE_ID_AFTER            =            "Issues|Issue"            MSG            =            "            $1            "            # Check for, and add if missing, a unique Change-Id            #            add_ChangeId()            {            clean_message            =            `sed -e            '                          /^diff --git a\/.*/{                          s///                          q                          }                          /^Signed-off-by:/d                          /^#/d                          '            "            $MSG            "            |            git stripspace`            if            test            -z            "            $clean_message            "            so            render            fi          

You will also get a missing Modify-ID message when trying to merge (git cherry-selection) some modify from git that does not have Change-ID. It seems that the hook isn't called by red-selection, but it is fortunately chosen by git commit -c some-commit-id .

In the example below we will be moving trivial modify bd7a268e4be2da23ba0b9943c3b0ba1ac88294dc from git master in the mediawiki/cadre project to REL1_19.

To fix this, use -n (don't commit) option to git ruddy-pick:

            git cherry-pick -n bd7a268e4be2da23ba0b9943c3b0ba1ac88294dc git commit -c bd7a268e4be2da23ba0b9943c3b0ba1ac88294dc          

Unfortunately, if yous want to add the original commit ID to the message (as washed past git cherry-pick -x) yous take to add information technology yourself.

If you lot forgot to run git review -s, "remote" will mutter virtually "missing Change-id in commit message".

But information technology volition likewise suggest a commit message with a Change-Id: INNNXXXNNN... line.

Either:

• Copy that line starting with "Modify-Id", run git commit --meliorate, and paste the Alter-Id line under your commit message in the text editor that opens upward.
• Or it will propose a claw fix:

                                  gitdir                =                $(git rev-parse --git-dir)                ;                scp -p -P                29418                freephile@gerrit.wikimedia.org:hooks/commit-msg                ${                gitdir                }/hooks/              

Yous should be able to use either method (but the hook didn't piece of work for me), then echo git review -R and information technology should complete.

git-review complains "You accept more than one commit that you are about to submit" [edit]

If git review displays a alarm about multiple commits, followed past a list of other people'south commits that have already been merged, perform the post-obit workaround:

1. Respond "no" to abort git-review.
2. Run git fetch --all or git remote update (Both commands do exactly the same thing, they fetch objects from all remote repositories set. Then just pick the command you remember easily and forget virtually the other i.)
3. Rerun git-review

This will ensure git-review has an up-to-date view of the remote master.

Groundwork [edit]

This was fixed in 2012 just the problems returned. Wikimedia projects suffer from this disproportionately because defaultrebase=0 is set on most Wikimedia projects, and the bug merely triggers when rebasing is disabled (using either that setting or the -R flag).

git-review complains "Cannot query patchset data" [edit]

git-review does non work correctly if git generates not-English language output. You volition see an error like this:

                        $            git review -d            62474            Cannot query patchset information            The following command failed with get out lawmaking 255                          "ssh -x -p None gerrit query --format=JSON --electric current-patch-set alter:62474"            -----------------------            Bad port ' None'            -----------------------          

This is due to a bug in git-review.

To work around this on a Linux system, either apply the patch from the bug report higher up, or set up an allonym that forces git to utilize English output. To exercise and so, put this into your bashrc or similar setup file:

git-review complains "ConfigParser.NoSectionError: No department: 'updates'" [edit]

If this happens (phab:T57732, fixed in newer git-review versions):

                        $            git review -s            Traceback (virtually contempo telephone call last):                          File "/usr/local/bin/git-review", line 1196, in <module>                          primary()                          File "/usr/local/bin/git-review", line 1108, in main                          needs_update = latest_is_newer()                          File "/usr/local/bin/git-review", line 179, in latest_is_newer                          if non configParser.getboolean("updates", "bank check"):                          File "/usr/lib/python2.vii/ConfigParser.py", line 368, in getboolean                          five = self.get(section, option)                          File "/usr/lib/python2.7/ConfigParser.py", line 607, in become                          raise NoSectionError(department)            ConfigParser.NoSectionError: No department: 'updates'          

Adding something similar this to ".gitreview" fixes the trouble:

git-review doesn't like merge commits [edit]

If y'all merged a development branch, and now desire to submit a merge commit to Gerrit, git review may not let you lot. Information technology may enquire you for submitting lots of changes from i of the merged branches, or otherwise mangle the commit. To avoid this, button the commit directly to Gerrit, bypassing git review:

            git push gerrit HEAD:refs/for/principal          

For more data, run across the Gerrit documentation.

git-review complains "Working tree is dirty" [edit]

If upon doing 'git review' yous receive a message "Working tree is dirty" attempt doing 'git add' for the file(southward) changed (or created), then git commit, and then git review. (This was seen on Mac OS 10 with an older git client.)

git-review complains "Authentication failed" [edit]

If you see

            remote: Unauthorized fatal: Authentication failed for 'https://gerrit.wikimedia.org/r/some/code/repository'          

then y'all are trying to push via HTTPS instead of SSH which you lot had set upward earlier. Y'all likely want to configure git to use the SSH remote instead of the HTTPS remote.

Gerrit [edit]

Gerrit complains that "Your modify could not be merged due to a path conflict" [edit]

Yous have to rebase your change in order to be able to merge it.

For the impatient:

git checkout master git pull git-review -d <change #> git rebase origin/primary git status <edit "both modified" files in status report> git add <files> git rebase --continue git review          

Total explanation [edit]

Gerrit does non magically resolve conflicts :)

So you have submitted a change and was approved. Just by the time it gets reviewed other commits have altered the main repository which now cause a conflict. Gerrit is unable to automatically merge your change into the repository, y'all will have to fix it and resubmit the change.

The instance below is based on a real utilize example : alter 2514 using the operations/puppet repository

Kickoff fetch the change using git-review and its -d choice :

                        (production)            $            git-review -d            2514            Downloading refs/changes/xiv/2514/1 from gerrit into review/hashar/ignore_pyc            Switched to branch 'review/hashar/ignore_pyc'            (review/hashar/ignore_pyc)            $          

hashar is the user name, ignore_pyc the topic name he gave. Notice how git-review automatically placed you to the co-operative.

You now have to rebase on top of the main branch. The change on gerrit shows the co-operative, but add "gerrit/" in front. For this alter in the operations/puppet repo, the master co-operative is "product", and so rebase on gerrit/production; for other repos it's normally origin/chief.

                        (review/hashar/ignore_pyc)            $            git rebase gerrit/production            First, rewinding head to replay your piece of work on tiptop of it...            Applying: pyc files are at present ignored            Using alphabetize info to reconstruct a base tree...            Falling dorsum to patching base and three-way merge...            Auto-merging .gitignore            Conflict (content): Merge conflict in .gitignore            Failed to merge in the changes.            Patch failed at 0001 pyc files are now ignored                                    When you take resolved this problem run "git rebase --continue".            If you would adopt to skip this patch, instead run "git rebase --skip".            To check out the original co-operative and stop rebasing run "git rebase --abort".            (no branch)            $          

The key in the above output is the line starting with Conflict. Information technology tells you the filename that git couldn't cleanly rebase, ordinarily because your patch alters information technology and changes in the master branch have also altered it. Running git status confirms information technology:

                        (no branch)            $            git status            #            Non currently on whatever co-operative.            #            Unmerged paths:            #                        (use            "git reset Caput <file>..."            to unstage)            #                        (employ            "git add/rm <file>..."            as appropriate to mark resolution)            #            #            both modified:      .gitignore            #            (no co-operative)            $          

Edit the conflicting file (in this case .gitignore). This will have <<<<, ==== >>> markers surrounding the alien lines, you lot must clean this upwardly. During the merge disharmonize git creates file.Base.30 , file.LOCAL.30 , and file.REMOTE.thirty files with the three source versions. You tin can use a three-way merge tool to choice which lines to use; git mergetool wraps the apply of a merge tool.

Once you lot have finished editing, you have to add together that modification to have information technology used during the rebase then continue fixing whatever conflicting patches:

                        (no branch)            $            git add .gitignore            (no branch)            $            git rebase --go along            Applying: pyc files are at present ignored            (review/hashar/ignore_pyc)            $          

Since there was no more patches to fix, you take been placed back in the review/hashar/ignore_pyc branch. Looking at the log:

                        $            git log -n5 --decorate --pretty=oneline            * a3631d2 (HEAD, review/hashar/ignore_pyc) pyc files are at present ignored (ii seconds agone            * 1b6cd67 (gerrit/production, production) ensure sample config file removed (18 hours agone)            ...          

Verify you change looks fine earlier resubmitting information technology to gerrit. Just use git testify <sha1 of commit>, i.east. git show a3631d2. You can somewhen amend it to state you accept rebased the modify.

Now submit your change back in the repository:

                        (review/hashar/ignore_pyc)            $            git review            remote: Resolving deltas:   0% (0/ii)            To ssh://<someuser>@gerrit.wikimedia.org:29418/operations/boob.git            (review/hashar/ignore_pyc)            $          

Heading back to Gerrit, the modify is a new patchset pending review.

Congratulations on fixing your kickoff rebase / merge conflict!

In Gerrit your change is non merged after receiving a +2 [edit]

If someone enters +2 Lawmaking Reviewed, it should trigger a series of automatic builds and tests. Continuous integration/Workflow describes the menstruum.

In Gerrit, the "user" jenkins-bot should add together a annotate

Starting gate-and-submit jobs. https://integration.wikimedia.org/zuul/

Follow the link to encounter the progress of the tests for your change that Zuul has submitted to Jenkins.

If you don't see the "Starting gate-and-submit jobs" comment in gerrit, look at https://integration.wikimedia.org/zuul/ It shows everything that Zuul has submitted to Jenkins, and the "Queue length" number on top is the number of events non still processed. If your task doesn't appear below this on the page beneath but the queue length is non-aught, it is likely in the queue; Zuul and Jenkins are probably busy and you lot just take to wait. Only if the queue length is 0 and your change doesn't appear, it means information technology isn't going to happen and yous need to resubmit it. Notation that new repos have to be manually added to jenkins-bot's list.

If the required tests all pass (notation that some are "not-voting"), and then jenkins-bot volition add a comment "Build succeeded" followed past "Modify has been successfully merged into the git repository."

In Gerrit Jenkins gave a -ii and then y'all need to override Jenkins [edit]

First of all, you should more or less never do this. (So far the reason was backporting a change to an old release that had broken tests). If Jenkins has a -2 you lot generally tin't merge the change. What you need to do:

• Removing the jenkins-bot "Verified" review (click the [x])
• Review the latest patch set with "Verified +ii" in improver to "Lawmaking-Review +2" (this is normally reserved for Jenkins, but since we're overriding it we're replacing its score with our ain)
• Click "Publish and Submit"

"Permission denied (publickey)" fault [edit]

fatal: Could not read from remote repository. [edit]

If you lot get the error

            Permission denied (publickey). fatal: Could not read from remote repository. Delight make sure you take the correct admission rights and the repository exists.          

And then please share the output of the command git remote show origin, run the affected git control with debug logging variables such equally GIT_CURL_VERBOSE=1 GIT_TRACE=1, and test if ssh -p 29418 username@gerrit.wikimedia.org (replace

username

in that command with your developer business relationship'south username!) shows Hi username, you have successfully continued over SSH.

fatal: The remote end hung upward unexpectedly [edit]

If you get the error

            Permission denied (publickey). fatal: The remote terminate hung up unexpectedly          

And then you're not logged in to your ssh central right now. Solution: practice ssh-add ~/.ssh/id_rsa to make it prompt you for the passphrase for your primal and add information technology to the agile keychain. Then you lot tin can check what's in your keychain with ssh-add -fifty. And so attempt pushing for review again.

The fingerprint of the Gerrit server is

dc:e9:68:7b:99:1b:27:d0:f9:fd:ce:6a:2e:bf:92:e1        

so you can say aye when it asks you to add that fingerprint to the known_hosts file.

Proceed in mind that gerrit listens on port 29418 and if for some reason you forgot to specify port number, you might be hitting "normal" SSH daemon listening on port 22 (this ane has RSA primal fingerprint b5:e9:dc:b2:dd:6e:lxx:f7:eighteen:8a:dc:a3:5d:ab:99:4d).

To check whether SSH connectivity and public key authentication, use ssh -p 29418 username@gerrit.wikimedia.org which should bear witness How-do-you-do username, yous take successfully connected over SSH.

Your change is not having tests run [edit]

Tests are just run users in the CI allow list. See Continuous integration/Permit list for more information.

Miscellaneous [edit]

Push using HTTPS (when SSH is non functional) [edit]

Due to a security incident, https push access has been (temporarily?) disabled. The following section may therefore not be applicable.

Extended content

This method is helpful for submitting to changes to Gerrit when SSH is not functional (for instance SSH is blocked by your institution or cyberspace provider). If SSH is not working, you should see one of these fault letters: ssh: connect to host gerrit.wikimedia.org port 29418: Connectedness refused ssh: connect to host gerrit.wikimedia.org port 29418: Network is unreachable Yous can also explicitly attempt the command ssh -p 29418 your-user-name@gerrit.wikimedia.org If SSH is functional, that command should create the post-obit output: Connection to gerrit.wikimedia.org closed by remote host. Connection to gerrit.wikimedia.org closed. When SSH is not functional, you need an HTTP(S) Password which can exist generated in the Account Settings of Gerrit nether "HTTP Password". After generating the password, commit all the changes for your patch(southward) and use git push https://<username>@gerrit.wikimedia.org/r/mediawiki/core HEAD:refs/for/master The authentication credentials need to exist entered to successfully submit the changes. The url given above is for MediaWiki core and will vary for extensions accordingly. For example if you want to push button to Extension:LiquidThreads the command would be git push button https://<username>@gerrit.wikimedia.org/r/mediawiki/extensions/LiquidThreads Caput:refs/for/primary To always apply https, initially clone with: git clone https://<username>@gerrit.wikimedia.org/r/mediawiki/core Or adapt an existing repository with: git remote gear up-url origin https://<username>@gerrit.wikimedia.org/r/mediawiki/core Then you tin apply git review normally. You can use git-credential-shop to store your HTTPS password so y'all don't have to type it in every time. Commit Hook and Change-ID [edit] A major problem that arises when using HTTPS for submitting changes is that commit hook is not automatically fastened. A hack for this approach is to make ane fail endeavour to push. On doing so, the fault bulletin volition automatically highlight the Change-Id, see below example: Username for 'https://gerrit.wikimedia.org': xxxxxx Password for 'https://xxxxxx@gerrit.wikimedia.org': Counting objects: 25, done. Delta pinch using up to ii threads. Compressing objects: 100% (iv/4), done. Writing objects: 100% (four/iv), 448 bytes | 0 bytes/s, done. Total 4 (delta iii), reused 0 (delta 0) remote: Resolving deltas: 100% (3/three) remote: Processing changes: refs: ane, done remote: ERROR: missing Change-Id in commit bulletin footer remote: Suggestion for commit bulletin: remote: Commit bulletin appears here remote: remote: Change-Id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx remote: remote: Hint: To automatically insert Change-Id, install the hook: remote: gitdir=$(git rev-parse --git-dir); scp -p -P 29418 xxxxxx@gerrit.wikimedia.org:hooks/commit-msg ${gitdir}/hooks/ remote: remote: To https://gerrit.wikimedia.org/r/mediawiki/extensions/Exam  ! [remote rejected] Head -> refs/for/master (missing Change-Id in commit message footer) fault: failed to push some refs to Now re-create the modify ID and amend your commit. Always add Change-ID every bit the terminal line of your commit message. git commit --meliorate This volition open an editor to modify the commit message. Paste the Change-Id equally the last line of the bulletin and save it. Come across example: Your commit summary Your commit message Issues: Txxxxx Change-Id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Now you can successfully push to Gerrit. Automatically adding commit Hook [edit] To obtain the commit-msg script: scp -p -P 29418 USERNAME@gerrit.wikimedia.org:hooks/commit-msg <local path to your git>/.git/hooks/ See https://gerrit.wikimedia.org/r/Documentation/cmd-hook-commit-msg.html for details. Beingness behind a proxy server [edit] This section is untested; please update this section with updated information if issues ascend If you lot are behind a proxy server, you too demand to clone over HTTPS. Make sure the environment variable HTTPS_PROXY is set correctly. To debug issues, try running with GIT_CURL_VERBOSE=ane, e.g. GIT_CURL_VERBOSE = 1 git clone https://gerrit.wikimedia.org/r/pywikibot/core.git In case of problems, effort providing HTTPS_PROXY directly, e.g. HTTPS_PROXY =proxy_server GIT_CURL_VERBOSE = i git clone https://gerrit.wikimedia.org/r/mediawiki/core.git or use git'due south options directly: GIT_CURL_VERBOSE = 1 git -c http.proxy= "proxy_server" clone https://gerrit.wikimedia.org/r/mediawiki/cadre.git This last option should also piece of work for SOCKS proxy servers, using GIT_CURL_VERBOSE = ane git -c http.proxy= "socks5://socks_server" clone https://gerrit.wikimedia.org/r/mediawiki/core.git

Push button using SSH simply (when HTTPS is disabled not functional) [edit]

Add to your local '.gitconfig' following section:

                        # Utilise SSH over HTTPS            [url "ssh://username@gerrit.wikimedia.org:29418/"]            pushInsteadOf            =            https://gerrit.wikimedia.org/r/          

"git commit --better" complains "you lot are in the middle of a merge -- cannot amend" [edit]

When after rebasing and merging your

results in

            message: fatal: You lot are in the middle of a merge -- cannot amend.          

utilize these steps and reapply your changes

            git stash git reset --hard git checkout principal git review -d <alter number> git stash pop git commit -a --better          

If, after git review jenkins-bot emails This change was unable to be automatically merged with the current state of the repository. Delight rebase your change and upload a new patchset. This might mean that server master branch now has merge conflicts with your patch. Check advanced Gerrit usage to run across how to set them.

"Your alter requires a recursive merge to resolve" [edit]

If yous get the error "Your change requires a recursive merge to resolve", you need to rebase the change set against master.

1. Make certain your master co-operative is up to date: git pull origin master
2. Create and switch to a new branch in which to checkout the change ready with the conflict: git checkout -b BRANCHNAME
3. Checkout the conflicting modify set into this branch. You can copy/paste the correct control from the 'Download' department in the Gerrit review. It will look something like this: git fetch ssh://awjrichards@gerrit.wikimedia.org:29418/mediawiki/extensions/MobileFrontend refs/changes/fourteen/3414/3 && git checkout FETCH_HEAD
4. Rebase against master: git rebase chief
5. Push button the change to Gerrit for review: git review
6. Re-review the change gear up in Gerrit, and then submit the changes to be merged to master.

"[remote rejected] chief -> principal" and "failed to button some refs" [edit]

If button to a branch other than refs/for/master, you volition receive something along the lines of:

                        $            git push            Counting objects: 5, washed.            Delta compression using upward to 8 threads.            Compressing objects: 100% (3/three), done.            Writing objects: 100% (three/3), 709 bytes, done.            Total 3 (delta one), reused 0 (delta 0)            remote: Resolving deltas:   0% (0/1)            To ssh://username@gerrit.wikimedia.org:29418/test/mediawiki/extensions/examples             ! [remote rejected] master -> master (prohibited past Gerrit)            error: failed to push some refs to 'ssh://username@gerrit.wikimedia.org:29418/test/mediawiki/extensions/examples'          

This ways you tried to commit to co-operative "master" instead of submitting your changes for review.

The post-obit is a similar error where git review was trying to push to a not-existing remote co-operative:

            ! [remote rejected] T12345 -> T12345 (prohibited by Gerrit) error: failed to push button some refs to 'ssh://username@gerrit.wikimedia.org:29418/test/mediawiki/extensions/examples'          

You can encounter with git branch what's the co-operative you're currently using. Try rebasing to button correctly:

            git pull --rebase origin chief git review -R          

"[remote rejected] HEAD -> refs/publish/master/??? (Cannot merge change to another co-operative) [edit]

When attempting to reddish-pick a alter or merge an unabridged co-operative and so submit for review; gerrit volition be very confused if you do not explicitly tell it what branch you lot're modifying. Y'all might go errors similar:

            ! [remote rejected] HEAD -> refs/publish/main/mwalker_test (change 59546 airtight)          

or

            ! [remote rejected] HEAD -> refs/publish/principal/mwalker_test (no new changes)          

In this example you must ensure that your branch's .gitreview file has the correct defaultbranch option (e.thousand. it should be pointing to the branch you're attempting to modify) or you must manually push the refspec using git button gerrit HEAD:refs/for/<branch>

! [remote rejected] HEAD -> refs/publish/master (prohibited by Gerrit: not permitted: create) [edit]

If you apply git-review to submit patches to gerrit, make certain you lot have 1.27 or newer (not 1.26). git-review 1.26 does not work with Gerrit 3.

! [remote rejected] Head -> refs/changes/79/550379/2 (cannot add patch ready to 550379.) [edit]

This happens if you are not the original author (owner) of a modify (in this case 550379). To exist able to add a new patch set to a commit yous did non author, please request improver to the Trusted-Contributors group on Gerrit. Every member of this grouping is able to add together you on asking.

Committer email accost does not friction match your user account. [edit]

remote: Fault:  committer email address (email) remote: Error:  does not match your user account.        

There are 2 possible bug that could cause this mistake. If the email address that git pops back _is_ the email address yous intend to utilise with Gerrit, then you should add that email address in Gerrit, and make sure you click the confirmation link in the email Gerrit sends you. Then try pushing once again.

If, even so, git sends dorsum some nonsense email (similar i you don't utilize anymore, or a local mail address like root@localhost), you should do the following:

                        $            git config --global user.email yournewemail@example.org            $            git commit --amend --reset-author          

To practice information technology locally for simply that repo, instead practise:

                        $            git config user.email yournewemail@example.org            $            git commit --amend --reset-author          

Then, try pushing again.

Build failed due to merge disharmonize [edit]

After `git review` jenkins-bot emails This change was unable to exist automatically merged with the electric current state of the repository. Please rebase your change and upload a new patchset. This might mean that server master co-operative now has merge conflicts with your patch.

• Brand sure your master co-operative hard-reset to the gerrit's master (to avoid git review complaining about multiple commits)

                        $            git checkout chief            $            git fetch --all            $            git reset --hard origin/principal          

• Checkout for review, rebase, recommit

                        $            git review -d <patchNumber>            $            git rebase master            #            Ready merge conflicts and add them with            'git add'            $            git rebase --continue            $            git review -R          

If the mistake occurs even though you accept rebased your patch every bit higher up, endeavour making an arbitrary change to your commit message, and and then running git review once again (related to issues 53895).

"Everything upward-to-date" message after git push [edit]

If you attempt to practice 'git push button' after doing 'git commit' you may receive a response 'Everything up-to-engagement'. You have not pushed to the branch. You accept to exercise 'git review' to movement your changes to gerrit, and only from gerrit will the branch be updated. This seems to be a side effect of checking out master as a co-operative as of Feb 2012.

In some projects (e.g. test/) it is possible to do 'git push' instead of 'git review' and have the push succeed. It is probably ameliorate not to exercise that, every bit it confuses those who observe your changes later and don't know where they came from.

Tagging an extension doesn't piece of work [edit]

If you desire to tag your extension, you lot need to connect to gerrit using ssh, not https. In your .git/config, the remote url should look similar this:

                        [remote "origin"]            url            =            ssh://username@gerrit.wikimedia.org:29418/r/mediawiki/extensions/yourextension            fetch            =            +refs/heads/*:refs/remotes/origin/*          

To tag an extension, apply git tag followed past git push:

            git tag -a v1.4 -thousand            'my version 1.four'            git push button --tags          

Plugin install error: TypeError: self.onAction is not a function [edit]

If you run into this error delight hard refresh your browser cache.

For some the Ctrl + F5 or Shift + Ctrl + F5 (or any combination your browser wants) is not sufficient.

If y'all still run into the issue after pressing your browsers F5 combination, please try clearing your caches for good.

For instance on Firefox follow steps ane-six from

• https://support.mozilla.org/kb/how-articulate-firefox-enshroud#w_clear-the-cache

If you utilise a dissimilar browser, it should permit you to articulate buried spider web content somewhere in the setting also. Delight find that in your browser'southward help pages and follow the instructions.

robinsonlinto1947.blogspot.com

Source: https://www.mediawiki.org/wiki/Gerrit/Troubleshooting