terraform/CODEOWNERS
Line: 12: incorrect codeowner organization: hashicorp/terraform-azure Line: 12: no users/groups matched Line: 15: incorrect codeowner organization: hashicorp/tf-eco-hybrid-cloud Line: 15: no users/groups matched Line: 16: incorrect codeowner organization: hashicorp/terraform-core Line: 16: no users/groups matched Line: 19: incorrect codeowner organization: hashicorp/terraform-aws Line: 19: no users/groups matched Line: 20: incorrect codeowner organization: hashicorp/tf-eco-hybrid-cloud Line: 20: no users/groups matched Line: 23: incorrect codeowner organization: hashicorp/terraform-core Line: 23: no users/groups matched Line: 24: incorrect codeowner organization: hashicorp/terraform-core Line: 24: no users/groups matched Line: 25: incorrect codeowner organization: hashicorp/terraform-core Line: 25: no users/groups matched Line: 35: incorrect format
Martin Atkins eecbfbf2cc CODEOWNERS: gcs backend is maintained by team tf-eco-hybrid-cloud
The folks involved asked for us to use this broader GitHub team so that
it's easier to maintain both this and the kubernetes backend collectively.
2024-03-15 10:40:57 -07:00

35 lines
1.9 KiB
Text

# Each line is a file pattern followed by one or more owners.
# More on CODEOWNERS files: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
# Entries that are commented out have maintainers that are not in the
# HashiCorp organization and so cannot be automatically added as reviewers.
#
# We retain those as documentation of who agreed to maintain, but they
# cannot be used automatically by GitHub's pull request workflow and would
# make GitHub consider this file invalid if not commented.
# Remote-state backend # Maintainer
/internal/backend/remote-state/azure @hashicorp/terraform-azure
#/internal/backend/remote-state/consul Unmaintained
#/internal/backend/remote-state/cos @likexian
/internal/backend/remote-state/gcs @hashicorp/tf-eco-hybrid-cloud
/internal/backend/remote-state/http @hashicorp/terraform-core
#/internal/backend/remote-state/oss @xiaozhu36
#/internal/backend/remote-state/pg @remilapeyre
/internal/backend/remote-state/s3 @hashicorp/terraform-aws
/internal/backend/remote-state/kubernetes @hashicorp/tf-eco-hybrid-cloud
# Provisioners
builtin/provisioners/file @hashicorp/terraform-core
builtin/provisioners/local-exec @hashicorp/terraform-core
builtin/provisioners/remote-exec @hashicorp/terraform-core
# go.sum files should never cause automatic review requests because they only
# ever change in response to go.mod files (our PR checks would fail if not) and
# if a specific module has _only_ a go.sum update without an associated go.mod
# update then that represents that the update cannot affect the module, and
# the Go toolchain just needed to download something new to prove that.
#
# (The last match in the file "wins", so this overrides any explicit owner
# specified above when go.sum is the only file that changed.)
*/go.sum # no owner for these