Search results
Create the page "Git-review" on this wiki! See also the search results found.
- the => are aligned in the editor commit the changes $ git commit -a $ git review Send a message to the Community mailing list with the review URL and5 KB (603 words) - 14:46, 20 June 2019
- with our code review tool. The easiest way to get git-review is to use pip: pip install git-review 5.2) Next you need to ensure your fix is in a single9 KB (1,033 words) - 15:18, 7 November 2014
- MacOSx, or most other Unix-like systems, it is as simple as: pip install git-review There are other installation options detailed in the Developer's Guide6 KB (855 words) - 18:50, 9 October 2015
- git review - The same tool we use for submitting patches for review has some options that assist with the review process. See the git-review man page4 KB (568 words) - 00:43, 7 January 2015
- pip install git-review NOTE: Several Linux distributions (notably Fedora 16 and Ubuntu 12.04) are also starting to include git-review in their repositories4 KB (494 words) - 15:14, 17 December 2014
- that handy for the "git review -s" command later in the https://wiki.openstack.org/wiki/Magnum/Contributing#Setting_up_your_git_review_settings and https://wiki15 KB (1,768 words) - 09:52, 15 January 2018
- that handy for the "git review -s" command later in the https://wiki.openstack.org/wiki/Watcher/Contributing#Setting_up_your_git_review_settings and https://wiki15 KB (2,237 words) - 16:31, 25 March 2016
- it. git review -d [review-id] The review-id is located the number in the URL (check the screenshot for more details). Example git review -d 929794 KB (676 words) - 18:32, 5 December 2014
- others, it's time to use git-review. Once you have git-review installed, from the base of the project run the command git review. This will send the commits4 KB (634 words) - 19:39, 10 September 2014
- precedes "git review -s"; see Development Workflow). mkdir ~/code cd ~/code git clone git://git.openstack.org/openstack/nova.git cd nova git review -s git8 KB (1,186 words) - 22:39, 5 December 2016
- ask Git-review to configure your project to know about Gerrit so the Gerrit Change-Id Commit hook gets installed. To do so: cd zaqar git review -s7 KB (929 words) - 18:44, 5 December 2014
- iecutter Requirements : cookiecutter modulesync (>= 0.5.0) git git-review digest To make the boilerplating of a new Puppet module easier a script4 KB (539 words) - 23:28, 18 May 2016
- backport commit: git checkout stable/newton git cherry-pick <commit> git review stable/newton1 KB (243 words) - 09:26, 23 August 2017
- Install the git-review tool, which is the tool OpenStack uses to simplify submission of reviews to Gerrit. sudo pip install git-review Simply running13 KB (1,918 words) - 19:29, 12 March 2014
- packaging change as usual, then symply do: git commit -a -m "Some changes" git review Note that you shouldn't edit debian/changelog. This will be done by the6 KB (1,118 words) - 13:02, 23 September 2016
- GerritWorkflow/ja (section Git Review インストール)pip install git-review Ubuntu Precise (12.04) 以降では、git-review はディストリビューションに含まれており、 他のパッケージと同じにようにしてインストールできます。 apt-get install git-review Fedora17 KB (2,841 words) - 02:31, 20 January 2015
- RACK/Contributing/ja (section Installing git-review)pip install git-review git clone https://github.com/stackforge/rack.git cd rack git checkout -b [branch name] git review -s "git review -s"コマンド実行6 KB (938 words) - 07:33, 9 June 2015
- review request for the master branch $ git review To send review request for the stable branch $ git review stable/ocata Bugs are tracked in RDO issue5 KB (595 words) - 14:16, 14 February 2024
- openstack.org/stackforge/poppy cd poppy git checkout -b [branch name] git review -s Create a topic branch to hold your work and switch to it. If you are5 KB (809 words) - 18:34, 5 December 2014
- cookbook); do cd $i git commit -am 'stable/<release> release patch' git review cd .. done Now we have a new master, need to get it in sync with matching3 KB (534 words) - 12:48, 10 December 2019
- is created, do the following on the branch in openstack-manuals so that git review works automatically: Update the .gitreview file in openstack-manuals7 KB (1,067 words) - 07:23, 7 September 2016
- $VERSION.1 vi .gitreview # set defaultbranch=stable/$SERIES git commit -a git review stable/$SERIES NB: For Swift, it still makes sense to commit the the9 KB (1,188 words) - 16:11, 13 June 2016
- git clone git://git.openstack.org/$repo $repo (cd $repo; git review -s) else echo "Updating $repo" (cd $repo; git remote1 KB (182 words) - 02:51, 11 January 2014
- Mac, Ubuntu, Fedora, and RHEL are known to work. I haven't installed git review on Windows so I don't know if a Windows laptop would work. Have the First5 KB (762 words) - 16:02, 16 September 2013
- ot, openstack-infra/gerritlib, openstack-infra/gitdm, openstack-infra/git-review, openstack-infra/jeepyb, openstack-infra/jenkins-job-builder, openstack-infra/lodgeit7 KB (921 words) - 13:35, 21 May 2014
- "Adding <your_name> candidacy for <project_name>" Submit your candidacy: git review For example if John Doe wants to become the next Nova PTL, he needs to12 KB (790 words) - 22:21, 14 October 2015
- "Adding <your_name> candidacy for <project_name>" Submit your candidacy: git review For example if John Doe wants to become the next Nova PTL, he needs to18 KB (747 words) - 00:03, 25 March 2016
- commit -m "Adding <your_name> candidacy for TC" Submit your candidacy: git review After it's submitted to gerrit, verification and approval is being done6 KB (468 words) - 21:08, 3 March 2016
- commit -m "Adding <your_name> candidacy for TC" Submit your candidacy: git review After it's submitted to gerrit, verification and approval is being done6 KB (466 words) - 10:38, 12 October 2016
- org/#/c/716429/ ) git clone https://opendev.org/starlingx/app-NAME cd app-NAME git review -s ← // For Debian, this command might need to be used57 KB (7,692 words) - 19:28, 18 March 2024
- き事が若干あります。まず、「git-review」をインストールする必要があります。このツールは、我々のコードレビューツールで作業する為に、あなたのリポジトリと個々のパッチの幾つかの初期設定を手助けする「review」コマンドを git に追加します。git-review を入手する最も簡単な方法は、pip9 KB (1,958 words) - 23:32, 17 February 2013
- it. git review -d [review-id] The review-id is located the number in the URL (check the screenshot for more details). Example git review -d 929794 KB (676 words) - 18:36, 5 December 2014
- "your_email@youremail.com" Install git-review. (In addition to python3, and pip3 ) $ sudo pip install git-review Clone the GitHub project $ git clone9 KB (921 words) - 17:47, 25 November 2014
- openstack-ci/* openstack-dev/openstack-nose openstack-dev/pbr openstack-ci/git-review (should move under openstack-dev) openstack-dev/openstack-qa (dead)2 KB (294 words) - 23:29, 17 February 2013
- the Corporate CLA, if needed) <TODO Play with the sandbox to make sure `git review` is setup correctly> Setup your development environment Each project should4 KB (437 words) - 22:59, 13 April 2015
- that we can work together and reap the benefits of collaboration. I wrote git-review to help with change submission to Gerrit. I've been working on getting3 KB (488 words) - 23:29, 17 February 2013
- stable/x.x versions of the same commit). Use the same Change-Id and topic (git review -t bug/<id>) to make it easier to track down all backports for that bug42 KB (5,589 words) - 09:22, 6 May 2016
- MASTER: ie, change `HEAT_VERSION = ['4']` to `HEAT_VERSION = ['5']`. Use git review to review the master version number change Bump version in spec file4 KB (502 words) - 18:17, 28 July 2013
- changes: $ git commit -a -m "Added <yourusername> to Planet OpenStack" $ git review Contact OpenStack Infra team on IRC #openstack-infra or mailing list4 KB (575 words) - 18:40, 14 December 2016
- git clone https://github.com/openstack/neutron (2) Get patch git review -d patch_id (3) Rebase git rebase -i master # (Fix the conflicts)4 KB (642 words) - 21:22, 8 July 2013
- add a Change-ID to the commit message GIT_EDITOR=true git commit --amend git review -R $feature_branch The resulting review will contain the resolution of4 KB (639 words) - 15:38, 30 January 2019
- launchpad bugs and improve yours gerrit workflow ( スライド ) アカウントのセットアップ git review のインストール ssh のセットアップ プロジェクトのセットアップ gerrit ワークフロー ユニットテストの実行 review13 KB (1,456 words) - 05:31, 24 December 2014
- _conf.ini Install the CLI/client cd /opt/stack/python-neutronclient git review -d 111475 sudo python setup.py install Create Entities Using CLI/client4 KB (598 words) - 16:45, 13 January 2015
- yet, so it's basically static. To update e.g. nova: cd /opt/stack/nova git review -d <somereviewwitheverythingwewantinit> /opt/stack/venvs/nova/bin/pip10 KB (1,621 words) - 00:00, 8 November 2013
- launchpad bugs and improve yours gerrit workflow ( slides ) account setup git review installation ssh setup project setup gerrit workflow running unit12 KB (915 words) - 16:03, 12 January 2016
- launchpad bugs and improve yours gerrit workflow ( slides ) account setup git review installation ssh setup project setup gerrit workflow running unit12 KB (968 words) - 22:51, 12 August 2016
- launchpad bugs and improve yours gerrit workflow ( slides ) account setup git review installation ssh setup project setup gerrit workflow running unit12 KB (1,125 words) - 10:07, 19 November 2014
- seeing new contributors coming in. We've done a lot to make installing git review easier and specifically setting up the gerrit remote. So the very first82 KB (12,584 words) - 14:07, 17 October 2014
- I made a few comments, a few details need to be improved $ git review -d 813178 $ git review -x 811049 <deal with potential conflict and implement changes64 KB (10,020 words) - 21:14, 28 January 2022
- 2017-11-17 23:24:29 UTC git-review 1.26.0 released, adding support for Gerrit 2.14 and Git 2.15: https://pypi.org/project/git-review/1.26.0/ 2017-11-15 06:09:38396 KB (74,330 words) - 17:15, 10 May 2024
