-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Implement auto-labeling of issues and PRs #8345
Copy link
Copy link
Open
Labels
area/devopsInvolving development tools, procedures, documentation, services, and so onInvolving development tools, procedures, documentation, services, and so onhelp wantedContributions welcome!Contributions welcome!kind/feature-requestDescribes new functionalityDescribes new functionalityno QC knowledge neededWant to contribute to Cirq, but don't know quantum computing? This issue is for you.Want to contribute to Cirq, but don't know quantum computing? This issue is for you.priority/p3Should be done in the next 6 monthsShould be done in the next 6 monthsskill/experiencedNeeds experience with Cirq developmentNeeds experience with Cirq developmenttriage/acceptedA consensus emerged that this bug report, feature request, or other action should be worked onA consensus emerged that this bug report, feature request, or other action should be worked on
Description
Activity
Metadata
Metadata
Assignees
Labels
area/devopsInvolving development tools, procedures, documentation, services, and so onInvolving development tools, procedures, documentation, services, and so onhelp wantedContributions welcome!Contributions welcome!kind/feature-requestDescribes new functionalityDescribes new functionalityno QC knowledge neededWant to contribute to Cirq, but don't know quantum computing? This issue is for you.Want to contribute to Cirq, but don't know quantum computing? This issue is for you.priority/p3Should be done in the next 6 monthsShould be done in the next 6 monthsskill/experiencedNeeds experience with Cirq developmentNeeds experience with Cirq developmenttriage/acceptedA consensus emerged that this bug report, feature request, or other action should be worked onA consensus emerged that this bug report, feature request, or other action should be worked on
Is your feature request related to a use case or problem? Please explain
We try to tag issues and PRs with tags such as area/gates or area/performance to improve findability, but we currently do tagging manually on an ad hoc basis. There exist numerous GitHub Actions workflows for automatically labeling things based on such things as the paths to files they involve. We should put in place a workflow with a configurable list of labels and rules (kept separate from the workflow) so that we don’t have to spend time doing it and so that labeling is done more consistently.
Describe the solution you would prefer
How urgent is this for you? Is it blocking important work?
P3 – I'm not really blocked by it; it's an idea I'm proposing based on principle