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

feat: check .codeowner within directory if it is provided to for_file #77

Merged
merged 5 commits into from
Dec 1, 2023

Conversation

att14
Copy link
Contributor

@att14 att14 commented Sep 29, 2023

If a directory is provided to codownership for_file check that directory for the presence of a .codeowner file.

@att14 att14 force-pushed the codeowner-for-file-directory branch from 71fa38a to ef269d2 Compare September 29, 2023 22:51
Copy link
Contributor

@alexevanczuk alexevanczuk left a comment

Choose a reason for hiding this comment

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

This seems fine to me! @shageman would you be able to verify this on the Gusto codebase?

@att14 att14 force-pushed the codeowner-for-file-directory branch from ef269d2 to 961e9d1 Compare October 2, 2023 21:08
Copy link
Contributor

@pbomb pbomb left a comment

Choose a reason for hiding this comment

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

You will also need to bump the version in code_ownership.gemspec. That way, once tests pass on main, the new gem will automatically be pushed to rubygems without any additional work.

@att14 att14 requested a review from pbomb October 3, 2023 21:34
@perryqh
Copy link
Contributor

perryqh commented Dec 1, 2023

We confirmed that this works with Gusto's codebase.

Please fix the conflicts and we'll merge the PR.

Thanks for the contribution!

@perryqh perryqh merged commit bd75d69 into rubyatscale:main Dec 1, 2023
4 checks passed
@att14 att14 deleted the codeowner-for-file-directory branch December 1, 2023 22:48
perryqh added a commit that referenced this pull request Dec 6, 2023
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.

5 participants