metadata.owner field in Ruby package.yml files not being respected

[joshuaylee]

Summary

The code_ownership documentation states that Ruby packages support ownership via both:

1. Top-level owner field
2. Nested metadata.owner field

However, the codeowner-rs documentation only mentions the top-level owner field. The code suggests metadata.owner is not currently supported for Ruby packages (though it is supported for JavaScript packages).

Expected Behavior

Ruby package.yml files should support ownership in either format:

  # Format 1: top-level owner
  owner: TeamName

  # Format 2: nested metadata.owner
  metadata:
    owner: TeamName

Current Behavior

Only Format 1 is supported (with code_ownership 2.0.0 and RustCodeOwners.version returning 0.3.0)

Questions

1. Is the code_ownership documentation correct? Should codeowners-rs support metadata.owner for Ruby packages, to support the previous behavior of code_ownership?
2. If yes, how should it handle conflicts when both fields are present (e.g., precedence rules or validation warnings)?
3. If no, should the code_ownership docs be updated to remove mention of metadata.owner support?

I'd be happy to submit a PR in codeowner-rs or code_ownership depending on the direction.

[martinemde]

thanks for the submitting this @joshuaylee. This seems like a regression, but I'm not sure which is the best path.

I do like keeping it simple with a single key, but I don't want to decide that on my own if it causes a lot of problems for other teams. Is there a reason to support the metadata key as well?