commenters[author_name] += 1
        for review in pr.reviews.nodes:
            if review.author:
                authors[review.author.login] = review.author
                pr_reviewers.add(review.author.login)
                for label in pr.labels.nodes:
                    if label.name == "lang-all":
                        translation_reviewers[review.author.login] += 1
                        break

      },
      "protocol": "HBONE",
      "uid": "Kubernetes//Pod/bookinfo/reviews-v3-5b9bd44f4-7fff4",
      "name": "reviews-v3-5b9bd44f4-7fff4",
      "namespace": "bookinfo",
      "trustDomain": "cluster.local",
      "serviceAccount": "bookinfo-reviews",
      "workloadName": "reviews-v3",
      "workloadType": "deployment",
      "canonicalName": "reviews",
      "canonicalRevision": "v3",
      "network": "network3",

                                    "tlsMode": "istio"
                                },
                                "istio": {
                                    "workload": "reviews-v3;default;reviews;v3;Kubernetes"
                                }
                            }
                        },
                        "loadBalancingWeight": 1
                    },
                    {

      loadBalancingWeight: 1
      metadata:
        filterMetadata:
          envoy.transport_socket_match:
            tlsMode: istio
          istio:
            workload: reviews-v3;default;reviews;v3;Kubernetes
    - endpoint:
        address:
          socketAddress:
            address: 10.244.0.193
            portValue: 9080
        healthCheckConfig: {}
      healthStatus: HEALTHY

Consultez les documents concernant <a href="https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews" class="external-link" target="_blank">l'ajout d'un review de pull request</a> pour l'approuver ou demander des modifications.

///

* During code reviews that introduce new APIs, reviewers need to be mindful that all new properties are implemented with lazy types.

kind: VirtualService
metadata:
  name: invalid-virtual-service
spec:
  http:
`
	warnDestinationRule = `apiVersion: networking.istio.io/v1
kind: DestinationRule
metadata:
  name: reviews-cb-policy
spec:
  host: reviews.prod.svc.cluster.local
  trafficPolicy:
    outlierDetection:
      consecutiveErrors: 7
`
	invalidYAML = `
(...!)`
	validKubernetesYAML = `
apiVersion: v1
kind: Namespace

    # Messages to create or check
    new_translation_message = f"Good news everyone! 😉 There's a new translation PR to be reviewed: #{pr.number} by @{pr.user.login}. 🎉 This requires 2 approvals from native speakers to be merged. 🤓"
    done_translation_message = f"~There's a new translation PR to be reviewed: #{pr.number} by @{pr.user.login}~ Good job! This is done. 🍰☕"

    # Normally only one language, but still
    for lang in langs:

* Add the specific language label.
* Add the label `awaiting-review`.

The label `awaiting-review` is special, only used for translations. A GitHub Action will detect it, then it will read the language label, and it will update the GitHub Discussions managing the translations for that language to notify people that there's a new translation to review.

    TensorFlow has passed version 1.0 and hence cannot make
    non-backward-compatible API changes without a major release. Reviewers of
    your pull request will comment on any API compatibility issues
    [following API review practices](https://github.com/tensorflow/community/blob/master/governance/api-reviews.md).
*   When you contribute a new feature to TensorFlow, the maintenance burden is