First login, clickSummary, description, Testingdone, branch, Group, people , Review upload diff file, select project, New Request Publish Released: Review Board Support Pre-commit Review and Post-commit Review two modes, in short, is the first Review to submit or first commit code to do Review. Each mode does not have to be mandatory, each project group can customize the review process two modes are mainly different from the way diff gets: git diff--full-index > D.diff Generate uncommitted diff file, initiate review request, Post-Commit git diff [git version number] [git version number] > D.diff commit to Git first, generate diff file, initiate review request*git diff ignores some files if the version number in the diff git repository does not report git catfile errors, you can delete theseHttp://www.jianshu.com/p/8ec1b32f2e13Recently encountered a demand: I need to change the code between some two commits, to the other children's shoes to apply, but in the diff I would like to ignore some of the files (such as the automated generation of similar build.js,dist.js files). So he did some tinkering and found the following solution:
- Set Git-diff Custom Driver
- Set the path and rules to ignore in the gitattributes, making the Git-diff of Build.css and build.js a direct effect
Set Git-diff driverGit supportCustom diff drive(See the description of the Diff.driver.command), meaning that Git-diff can specify a command to run, instead of running the built-in. With this configuration support, we can set the following Nodiff instructions (in the project Root path):git config diff.nodiff.command/usr/bin/trueWhat about this order? This command does nothing and returns True (/usr/bin/true) directly, which results in a similar skip effect.set up git attributesAbout git attributes can be seen directlyOfficial Document Description, we use this feature to create a. gitattributes file in the project root directory, and add the following configuration:build.css diff=nodiff build.js diff=nodiffOkay, now we can connect and understand, when we run the git diff command, Git will read the configuration of the. Gitattributes and then find that when encountering the Build.css and build.js files, the Nodiff instructions need to be executed, and the Nodiff instruction is configured as/usr/bin/true directly to return true, so , it just "skips". Here the file path configuration and. Gitignore are the same, supporting directories, files, wildcards and the like, can be easily implemented to ignore a batch of files or the entire directory.* Most Windows adapts to this approach and requires more manual action. The easy way is to install Rbtools, refer to the blog http://blog.csdn.net/fengyishang/article/details/50353196http://blog.csdn.net/irene_jia/article/details/125690651. Python 2.x, preferably 2.7. As is known to all, Python 3.0 has significant changes and 2.x scripts cannot run on 3.0. 2. Install Python setuptools Installer fromhttps://pypi.python.org/pypi/setuptools#windowsThen add the Python27 directory and the python27\scripts directory to the environment variable path. 3. ez_setup.py the file fromhttp://peak.telecommunity.com/dist/Copied locally to the client. 4. Run from the command-line window: Python ez_setup.pyhttp://www.reviewboard.org/docs/manual/1.7/users/tools/post-review/ created a topic on git. Branch to complete a function or modify a problem point, after the completion of the submission of review, as long as you enter the command post-review on this branch, the system will automatically create a branch since the creation of all the modifications and together, sent to the server to create a review request.
- If you just want to ask someone to review the last commit you made on the master branch, just command
Post-review--parent=head^
- If you want to invite people to review the most recent commit on the master branch, such as the last four commits, you only need to enter
Post-review--parent=head~4
- If you want to ask a person to review multiple commits in any time period on the Master branch, just enter Post-review--revision-range=startrev:stoprev or Post-review-- Revision-range=revnum commit a version of a history
- If you want to modify the results for review and submit the review again, simply enter
Post-review-r 54, where 54 is the review request Number8 shown on the Review Board page. Usually when running the Post-review command, the system will be required to enter the review Board login account (username/password), in order to avoid repeated input, you can edit the local git repository. git directory config file, in the [alias] Add a line to the section: Post-review =!post-review--guess-summary--guess-description--username=<your USERNAME>-- Password=<your password> this way, in the future need to run Post-review place directly into the Git post-review, so that no longer enter the user name and password.
4. Review Board Normal User Ubuntu14.04
