• Get Review Board
  • What's New
  • Products
  • Review Board Code review, image review, and document review
  • Documentation
  • Release Notes
  • Power Pack Enterprise integrations, reports, and enhanced document review
  • Try for 60 Days
  • Purchase
  • RBCommons Review Board as a Service, hosted by us
  • Pricing
  • RBTools Command line tools and Python API for Review Board
  • Documentation
  • Release Notes
  • Review Bot Automated code review, connecting tools you already use
  • Documentation
  • Release Notes
  • RB Gateway Manage Git and Mercurial repositories in your network
  • Documentation
  • Release Notes
  • Learn and Explore
  • What is Code Review?
  • Documentation
  • Frequently Asked Questions
  • Support Options
  • Third-Party Integrations
  • Demo
  • Review Board RBTools Power Pack Review Bot Djblets RB Gateway
    1. RBTools 2.0
    2. Version 5.x
    3. Version 4.x
    4. Version 3.x
    5. Version 2.0
    6. Version 1.0
    7. Version 0.7
    8. Version 0.6
    9. Version 0.5
    10. rbt
    11. Commands
    12. patch
  • Home
  • rbt
  • Configuration
  • Repository Configuration
  • Per-User Configuration
  • Team Foundation Server Configuration
  • Commands
  • alias
  • api-get
  • attach
  • clear-cache
  • close
  • diff
  • install
  • land
  • list-repo-types
  • login
  • logout
  • patch
  • post
  • publish
  • setup-completion
  • setup-repo
  • stamp
  • status
  • status-update
  • RBTools Python API
  • Overview of the Python API Client
  • Tutorial
  • Resource-Specific Functionality
  • RBTools Workflows
  • Using RBTools with Git
  • Glossary
  • General Index
  • Release Notes
  • This documentation covers RBTools 2.0. You can select a version above or view the latest documentation.

    patch¶

    rbt patch will download the latest diff from the review request matching review-request-id and apply it to the local working directory. The --diff-revision option may be used to specify a specific revision of the diff to use.

    Usage¶

    $ rbt patch [options] <review-request-id>
    

    Options¶

    -c, --commit¶

    Commits using information fetched from the review request (Git/Mercurial only).

    New in version 0.5.3.

    -C, --commit-no-edit¶

    Commits using information fetched from the review request (Git/Mercurial only). This differs from --commit by not invoking the editor to modify the commit message.

    --diff-revision <revision>¶

    The Review Board diff revision ID to use for the patch.

    --px <num>¶

    Strips the given number of paths from filenames in the diff. Equivalent to patch’s -p argument.

    --print¶

    Prints the patch to standard output instead of applying it to the tree.

    New in version 0.5.3.

    -R, --revert¶

    Revert the given patch instead of applying it.

    This feature does not work with Bazaar or Mercurial repositories.

    New in version 0.7.3.

    --write¶

    Write the patch to a given file instead of applying it to the tree.

    New in version 2.0.1.

    --commit-ids¶

    Comma-separated list of commit IDs to apply.

    This only applies to review requests created with commit history.

    New in version 2.0.

    --squash¶

    Squash all patches into one commit. This is only used if also using -c/--commit or -C/--commit-no-edit.

    New in version 2.0.

    -d, --debug¶

    Displays debug output.

    This information can be valuable when debugging problems running the command.

    The default can be set in DEBUG in .reviewboardrc.

    Review Board Server Options¶

    Options necessary to communicate and authenticate with a Review Board server.

    --server <url>¶

    Specifies the Review Board server to use.

    The default can be set in REVIEWBOARD_URL in .reviewboardrc.

    --username <username>¶

    The user name to be supplied to the Review Board server.

    The default can be set in USERNAME in .reviewboardrc.

    --password <password>¶

    The password to be supplied to the Review Board server.

    The default can be set in PASSWORD in .reviewboardrc.

    --ext-auth-cookies <ext auth cookies>¶

    Use an external cookie store with pre-fetched authentication data. This is useful with servers that require extra web authentication to access Review Board, e.g. on single sign-on enabled sites.

    The default can be set in EXT_AUTH_COOKIES in .reviewboardrc.

    New in version 0.7.5.

    --api-token <token>¶

    The API token to use for authentication, instead of using a username and password.

    The default can be set in API_TOKEN in .reviewboardrc.

    New in version 0.7.

    --disable-proxy¶

    Prevents requests from going through a proxy server.

    The default can be set in ENABLE_PROXY in .reviewboardrc.

    --disable-ssl-verification¶

    Disable SSL certificate verification. This is useful with servers that have self-signed certificates.

    The default can be set in DISABLE_SSL_VERIFICATION in .reviewboardrc.

    New in version 0.7.3.

    --disable-cookie-storage¶

    Use an in-memory cookie store instead of writing them to a file. No credentials will be saved or loaded.

    The default can be set in SAVE_COOKIES in .reviewboardrc.

    New in version 0.7.3.

    --disable-cache¶

    Disable the HTTP cache completely. This will result in slower requests.

    The default can be set in DISABLE_CACHE in .reviewboardrc.

    New in version 0.7.3.

    --disable-cache-storage¶

    Disable storing the API cache on the filesystem, instead keeping it in memory temporarily.

    The default can be set in IN_MEMORY_CACHE in .reviewboardrc.

    New in version 0.7.3.

    --cache-location <file>¶

    The file to use for the API cache database.

    The default can be set in CACHE_LOCATION in .reviewboardrc.

    New in version 0.7.3.

    --ca-certs <file>¶

    Additional TLS CA bundle.

    The default can be set in CA_CERTS in .reviewboardrc.

    --client-key <file>¶

    Key for TLS client authentication.

    The default can be set in CLIENT_KEY in .reviewboardrc.

    --client-cert <file>¶

    Certificate for TLS client authentication.

    The default can be set in CLIENT_CERT in .reviewboardrc.

    Repository Options¶

    --repository <name>¶

    The name of the repository configured on Review Board that matches the local repository.

    The default can be set in REPOSITORY in .reviewboardrc.

    --repository-url <url>¶

    The URL for a repository.

    When generating diffs, this can be used for creating a diff outside of a working copy (currently only supported by Subversion with specific revisions or --diff-filename, and by ClearCase with relative paths outside the view).

    For Git, this specifies the origin URL of the current repository, overriding the origin URL supplied by the client.

    The default can be set in REPOSITORY_URL in .reviewboardrc.

    Changed in version 0.6: Prior versions used the REPOSITORY setting in .reviewboardrc, and allowed a repository name to be passed to --repository-url. This is no longer supported in 0.6 and higher. You may need to update your configuration and scripts appropriately.

    --repository-type <type>¶

    The type of repository in the current directory. In most cases this should be detected automatically, but some directory structures containing multiple repositories require this option to select the proper type. The rbt list-repo-types command can be used to list the supported values.

    The default can be set in REPOSITORY_TYPE in .reviewboardrc.

    Keep up with the latest Review Board releases, security updates, and helpful information.

    About
    News
    Demo
    RBCommons Hosting
    Integrations
    Happy Users
    Support Options
    Documentation
    FAQ
    User Manual
    RBTools
    Administration Guide
    Power Pack
    Release Notes
    Downloads
    Review Board
    RBTools
    Djblets
    Power Pack
    Package Store
    PGP Signatures
    Contributing
    Bug Tracker
    Submit Patches
    Development Setup
    Wiki
    Follow Us
    Mailing Lists
    Reddit
    Twitter
    Mastodon
    Facebook
    YouTube

    Copyright © 2006-2025 Beanbag, Inc. All rights reserved.

    Terms of Service — Privacy Policy — AI Ethics Policy — Branding

    On this page

    • [Top]
    • Usage
    • Options
      • Review Board Server Options
      • Repository Options