Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(github): update CODEOWNERS #1770

Merged
merged 1 commit into from Mar 29, 2024
Merged

ci(github): update CODEOWNERS #1770

merged 1 commit into from Mar 29, 2024

Conversation

lachieh
Copy link
Contributor

@lachieh lachieh commented Mar 27, 2024

Feature or Problem

@vados-cosmonic noticed this issue when viewing the .github/CODEOWNERS file which I think is caused by a capitalization in the team name. It might not, though, so 🤷‍♂️.
Screenshot 2024-03-27 at 9 57 49 AM

@lachieh lachieh requested a review from a team as a code owner March 27, 2024 14:18
Signed-off-by: Lachlan Heywood <lachieh@users.noreply.github.com>
@vados-cosmonic
Copy link
Contributor

So @lachieh the preview of the file in the PR actually still has the errors -- I think it's still a problem? I also see different cases (wasmCloud vs wasmcloud) in the picture from your description

image

@lachieh
Copy link
Contributor Author

lachieh commented Mar 27, 2024

Yeah, that's all that I changed. I'm thinking this is an issue with the repo permissions rather than the file itself.

@thomastaylor312, can you take a look to see that all these groups have write permission on this repo?

  • @wasmcloud/observability-maintainers
  • @wasmCloud/capability-provider-sdk-maintainers
  • @wasmCloud/capability-provider-wit-bindgen-maintainers
  • @wasmCloud/wascap-maintainers

@thomastaylor312
Copy link
Contributor

@lachieh none of those have access. Do they all need write level access or something else?

@lachieh
Copy link
Contributor Author

lachieh commented Mar 28, 2024

@thomastaylor312 Assuming they need write access but it might be solved with something lower. Probably makes sense to have write since those groups are responsible for at least part of the repo. The error that shows up when you view the CODEOWNERS file says there are issues:
https://github.com/wasmCloud/wasmCloud/blob/main/.github/CODEOWNERS

Copy link
Contributor

@thomastaylor312 thomastaylor312 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lachieh Should be good to go now. I added those teams with the proper access

@lachieh lachieh merged commit 37722bd into main Mar 29, 2024
53 checks passed
@lachieh lachieh deleted the ci/codeowners-fix branch March 29, 2024 22:27
@lachieh
Copy link
Contributor Author

lachieh commented Mar 29, 2024

Ok that solved it. Didn't really need to merge since apparently repos and groups are case-insensitive but merged anyway for naming consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants