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
