github/flutter
7
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2025-06-03 00:51:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove/replace the team label with c: contributor-productivity. (#168702)

Browse Source 
Closes https://github.com/flutter/flutter/issues/168513.

See @stuartmorgan-g's comments here, which seem solid to me:
https://github.com/flutter/flutter/issues/168513#issuecomment-2866610972.

---------

Co-authored-by: Kate Lovett <katelovett@google.com>
This commit is contained in:
Matan Lurey 2025-05-13 16:48:07 -07:00 committed by GitHub
parent 9bdbf497bc
commit f8a0e5794d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.github/dependabot.yml vendored
View File

@ -14,7 +14,6 @@ updates:
- "christopherfujino" - "christopherfujino"
- "jmagman" - "jmagman"
labels: labels:
- "team"
- "team-infra" - "team-infra"
- "autosubmit" - "autosubmit"
# Updating patch versions for "github-actions" is too chatty. # Updating patch versions for "github-actions" is too chatty.

6
.github/labeler.yml vendored
View File

@ -201,14 +201,10 @@ platform-windows:
- '**/fix_data.yaml' - '**/fix_data.yaml'
- '**/*.expect' - '**/*.expect'
- '**/*test_fixes*' - '**/*test_fixes*'
'c: contributor-productivity':
team:
- changed-files: - changed-files:
- any-glob-to-any-file: - any-glob-to-any-file:
- docs/about/**/*
- docs/contributing/**/* - docs/contributing/**/*
- docs/postmortems/**/*
team-android: team-android:
- changed-files: - changed-files:
- any-glob-to-any-file: - any-glob-to-any-file:

2
docs/infra/Flutter-Framework-Gardener-Rotation.md
View File

@ -50,7 +50,7 @@ Unmute the [tree-gardener channel] and [hackers-infra channel] on [Discord]. Con
Escalate to the [test owner][TESTOWNERS]. File GitHub issues if none are already open. Escalate to the [test owner][TESTOWNERS]. File GitHub issues if none are already open.
1. The title should include the name of the failing test. 1. The title should include the name of the failing test.
1. Assign the issue to the test owner with a `P1` priority. 1. Assign the issue to the test owner with a `P1` priority.
1. Add the `team` label. 1. Add the [`c: contributor-productivity`](https://github.com/flutter/flutter/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22c%3A%20contributor-productivity%22) label.
1. Include links to the failing tests. Download any relevant logs and attach them to the issue, even if the link to the failing tests has the same information. This prevents the issues from becoming stale when logs are expunged. 1. Include links to the failing tests. Download any relevant logs and attach them to the issue, even if the link to the failing tests has the same information. This prevents the issues from becoming stale when logs are expunged.
1. @ mention the test owner in the [tree-gardener channel] on [Discord] with a link to the GitHub issue. If they are unavailable, escalate to another team member. Continue escalating until someone acknowledges the issue is being investigated. 1. @ mention the test owner in the [tree-gardener channel] on [Discord] with a link to the GitHub issue. If they are unavailable, escalate to another team member. Continue escalating until someone acknowledges the issue is being investigated.

2
docs/infra/Packages-Gardener-Rotation.md
View File

@ -89,7 +89,7 @@ If old deprecations have reached the point where they can be fixed without losin
File GitHub issues if none are already open. File GitHub issues if none are already open.
1. The title should include the name of the failing test. 1. The title should include the name of the failing test.
1. Assign the issue to the test owner with a `P1` priority. 1. Assign the issue to the test owner with a `P1` priority.
1. Add the `team` label. 1. Add the [`c: contributor-productivity`](https://github.com/flutter/flutter/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22c%3A%20contributor-productivity%22) label.
1. Include links to the failing tests. Download any relevant logs and attach them to the issue, even if the link to the failing tests has the same information. This prevents the issues from becoming stale when logs are expunged. 1. Include links to the failing tests. Download any relevant logs and attach them to the issue, even if the link to the failing tests has the same information. This prevents the issues from becoming stale when logs are expunged.
1. @ mention the test owner in the [hackers-ecosystem channel] on [Discord] with a link to the GitHub issue. If they are unavailable, escalate to another team member. Continue escalating until someone acknowledges the issue is being investigated. 1. @ mention the test owner in the [hackers-ecosystem channel] on [Discord] with a link to the GitHub issue. If they are unavailable, escalate to another team member. Continue escalating until someone acknowledges the issue is being investigated.
1. Investigation updates and questions should not be posted in the [tree-status channel]. This channel should remain free of noise to discourage notification muting. 1. Investigation updates and questions should not be posted in the [tree-status channel]. This channel should remain free of noise to discourage notification muting.