Lists routed pull requests with the lane each took (blocked, fast, standard or approver), the risk, whether the checks are clean and whether the lane’s approval is in. Filter by lane. Any role may read it.
Usage
overlane pr list [--lane LANE]Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--lane |
one of blocked, fast, standard, approver |
no | Only this lane |
Examples
overlane pr list
overlane pr list --lane approver --jsonBehavior
- Effect:
read(changes nothing). - Needs credentials: yes. Uses the network: yes.
- Supports
--dry-run: no. Accepts--force: no. - Machine-readable description:
overlane schema pr list.
Result
With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.
{
"type": "object",
"properties": {
"tenantId": {
"type": "string"
},
"projectId": {
"type": "string"
},
"routes": {
"type": "array",
"items": {
"type": "object",
"properties": {
"repository": {
"type": "string"
},
"number": {
"type": "number"
},
"title": {
"type": "string"
},
"approved": {
"type": "boolean"
},
"route": {
"type": "object",
"properties": {
"lane": {
"type": "string"
}
},
"required": [
"lane"
],
"additionalProperties": {}
}
},
"required": [
"repository",
"number",
"title",
"approved",
"route"
],
"additionalProperties": {}
}
}
},
"required": [
"tenantId",
"projectId",
"routes"
],
"additionalProperties": false
}See exit codes for the status the process returns.