chore: Require codeowner for go.mod changes

[LKreutzer]

Signed-off-by: Lars Kreutzer lars.kreutzer@tngtech.com

Summary

• Currently the go.mod files are not owned by any codeowner group. Instead they are handled, together with the generated files, e.g. go.sum, by the non-existent @ghost group.
  • The go.mod files are generated, however they should be reviewed as they define the pinning of dependencies for Go builds.
• The problem with the current setup is that when PRs are opened that only change these files, e.g. by the dependabot, then no codeowner groups are notified and no codeowner approval is needed for any changes to these files.
  • See:
    • chore(deps): bump github.com/containerd/containerd from 1.3.2 to 1.5.16 in /cwf/k8s/cwf_operator #14843
    • chore(deps): bump github.com/aws/aws-sdk-go from 1.15.27 to 1.33.0 in /feg/radius/lib/go/oc #14804
    • chore(deps): bump github.com/Masterminds/goutils from 1.1.0 to 1.1.1 in /cwf/k8s/cwf_operator #14803
    • chore(deps): bump helm.sh/helm/v3 from 3.2.4 to 3.10.3 in /cwf/k8s/cwf_operator #14844
• The changes in this PR remove the go.mod files from the non-existent @ghost group and implicitly move them into the codeowner groups that own the folders where they are located.
  • Note that many go.mod files are located in cloud folders, which means that they are automatically owned via */cloud/ @magma/approvers-cloud.
  • All go.mod files are located in folders owned by codeowners.
• Resolves Investigate CODEOWNERS file settings for generated Go files #14868

Test Plan

• Verify that all go.mod files are owned by the approver groups.

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by PR DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

DP Lint & Test

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit b4f17b4.

[pshelar]

LGTM. Thanks.