Skip to content

Commit

Permalink
chore(samples): add cloud-retail-team as sample owners (googleapis#138)
Browse files Browse the repository at this point in the history
* Add cloud-retail-team to CODEOWNER

* update codeowner_team in .repo-metadata.json

* 🦉 Updates from OwlBot

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Anthonios Partheniou <[email protected]>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
  • Loading branch information
3 people authored Jan 28, 2022
1 parent 234883d commit ec1d8bc
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
8 changes: 4 additions & 4 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@
# https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#codeowners-syntax
# Note: This file is autogenerated. To make changes to the codeowner team, please update .repo-metadata.json.

# @googleapis/yoshi-python is the default owner for changes in this repo
* @googleapis/yoshi-python
# @googleapis/yoshi-python @googleapis/cloud-retail-team are the default owners for changes in this repo
* @googleapis/yoshi-python @googleapis/cloud-retail-team

# @googleapis/python-samples-reviewers is the default owner for samples changes
/samples/ @googleapis/python-samples-reviewers
# @googleapis/python-samples-reviewers @googleapis/cloud-retail-team are the default owners for samples changes
/samples/ @googleapis/python-samples-reviewers @googleapis/cloud-retail-team
2 changes: 1 addition & 1 deletion .repo-metadata.json
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,6 @@
"distribution_name": "google-cloud-retail",
"api_id": "retail.googleapis.com",
"default_version": "v2",
"codeowner_team": "",
"codeowner_team": "@googleapis/cloud-retail-team",
"api_shortname": "retail"
}

0 comments on commit ec1d8bc

Please sign in to comment.