| name: Technical Review | |
| description: Project technical review request | |
| title: '[Tech Review]:' | |
| labels: | |
| - kind/initiative | |
| - kind/tech-review | |
| body: | |
| - type: input | |
| id: name | |
| attributes: |
| # Define labels, description, color | |
| # Support ‘previous’ for label changes over time / changes in ownership | |
| # Apply/remove label based on condition and/or slash command | |
| # Apply labels based on file path | |
| # Treat labels as namespaced based on “path” (slash separated) | |
| labels: | |
| - name: foo | |
| color: 00ff00 |
| schema_version: v1.0 | |
| name: | |
| homepage_url: | |
| logo: | |
| description: | |
| crunchbase: | |
| twitter: | |
| release_url: | |
| # extra, mirrors landscape extra | |
| config: |
When a label configuration is supplied, they should be the only labels that exist.
When the label configuration is updated (name, color, description etc), it should update the label and all items the label was previously tagged with.
When a label that isn't defined is attempted to be applied, it should not create the label and prompt the user.
When there are multiple matching commands, it should it process all of them.
| autoCreateLabels: true | |
| autoDeleteLabels: false | |
| # Define labels, description, color | |
| # Support ‘previous’ for label changes over time / changes in ownership | |
| # Apply/remove label based on condition and/or slash command | |
| # Apply labels based on file path | |
| # Treat labels as namespaced based on “path” (slash separated) | |
