|
1 | 1 | # Cirq infra
|
2 | 2 |
|
3 |
| -This doc describes cirq-infra, the GCP project supporting our open source |
4 |
| -project. The following things are planned to be running on GCP: |
| 3 | +_Cirq-infra_ is the name of a the Google Cloud Platform (GCP) project implemented and managed by the |
| 4 | +Google Quantum AI team in support of open-source projects like Cirq. It was originally introduced |
| 5 | +around the years 2020–2021 to implement several systems: |
5 | 6 |
|
6 |
| -* [X] Cirq bot / PR monitor - see [../pr_monitor](../pr_monitor/README.md) |
7 |
| -* [X] Triage party for triaging |
8 |
| -* [ ] Performance tests and reports |
| 7 | +* Automatic merging of pull requests on GitHub |
| 8 | +* Automatic labeling of the sizes of changes in pull requests |
| 9 | +* Running [Triage Party](https://github.com/google/triage-party), a tool for collaborative |
| 10 | + triaging of GitHub issues and pull requests |
9 | 11 |
|
10 |
| -Access is granted to Cirq maintainers only. |
| 12 | +The automerge and automatic labeling capabilities were implemented using a homegrown tool called |
| 13 | +`pr_monitor`, whose source code was in the [`dev_tools`](../) subdirectory of the Cirq |
| 14 | +repository. In 2025, the automerge system was discontinued in favor of using GitHub's "merge |
| 15 | +queues", and the size-labeling facility was reimplemented using a GitHub Actions workflow. |
| 16 | +`pr_monitor` was retired in the Cirq 1.5 release. |
| 17 | + |
| 18 | +_Cirq-infra_ is still being used to support Triage Party. |
11 | 19 |
|
12 | 20 | ## GCP Configuration
|
13 | 21 |
|
| 22 | +Access is granted to Cirq maintainers only. |
| 23 | + |
14 | 24 | ### Requirements
|
15 | 25 |
|
16 | 26 | The tools below are required to manage our infra:
|
|
0 commit comments