| Crates.io | revq |
| lib.rs | revq |
| version | 0.1.1 |
| created_at | 2024-09-12 17:28:33.443547+00 |
| updated_at | 2024-09-15 18:09:36.689944+00 |
| description | Review and query your pull requests |
| homepage | https://github.com/k3ii/revq |
| repository | https://github.com/k3ii/revq |
| max_upload_size | |
| id | 1372991 |
| size | 735,115 |
revq is a command-line tool designed to streamline the process of reviewing, searching, and filtering GitHub pull requests.

You can install revq using one of the following methods:
If you have Rust's package manager, Cargo, installed, you can install revq with:
cargo install revq
For macOS users, you can install revq using Homebrew:
brew install k3ii/tap/revq
Check the release page to install the pre-built binaries.
The general syntax for using revq is:
revq [OPTIONS] [COMMAND]
-u, --username <USERNAME> Specify GitHub username-o, --org Use organization PRs-r, --req Show PRs where review is requested --all Show all PRs for organization (only works with --org)-h, --help Print help information-V, --version Print version informationList your pull requests:
revq
List pull requests for a specific user:
revq -u username
List your pull requests for your organization:
revq -o
List pull requests for a specific user in your organization:
revq -o -u username
List pull requests where your review is requested:
revq -r
List pull requests where your review is requested in your organization:
revq -r -o
List all pull requests for your organization:
revq -o --all
To get started with revq, follow these steps:
revq with your GitHub token:revq init
To reinitialize or update your configuration:
revq init --force
revq was born out of a desire to learn Rust programming and improve upon a simple bash script created by my mentor.
revq offers several advantages over similar tools like gh pr:
We have exciting plans for future enhancements to revq:
Contributions are welcome to revq! Please feel free to submit a Pull Request.
This project is licensed under the MIT License - see the LICENSE file for details.
If you encounter any problems or have any questions, please open an issue on our GitHub repository.