add cloud-artifacts as codeowners of /schemas/dbt

[MichelleArk]

resolves N/A

Description

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[MichelleArk]

https://github.com/orgs/dbt-labs/teams/cloud-artifacts

[MichelleArk]

From the GH docs:

Users and teams must have explicit write access to the repository, even if the team's members already have access.

@leahwicz - are we okay granting write access to @dbt-labs/cloud-artifacts, assuming they don't have it already?

[leahwicz]

Yeah that is fine. We have PR reviews enforced so its not like an accidental commit can be pushed

[aranke]

Long-term nit: this should be a CODENOTIFY file instead, so we're not blocked on the Cloud Artifacts review?

https://about.sourcegraph.com/blog/a-different-way-to-think-about-code-ownership

[leahwicz]

Yeah that is fine. We have PR reviews enforced so its not like an accidental commit can be pushed

[MichelleArk]

@aranke - I don't believe this will block merging on code review from Cloud Artifacts based on the behaviour I've been seeing for changes to files owned by existing codeowners defined.

Here's a recent example that modified core/dbt/adapters/base/impl.py, tagged Core - Adapters as codeowners, but did not require an approval to merge: #7307

I'll create a test PR to confirm the behaviour once this is merged though!