-
-
Notifications
You must be signed in to change notification settings - Fork 11
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: --output-path
flag for pizza generate codeowners
#223
Merged
nickytonline
merged 1 commit into
open-sauced:beta
from
udaypatel1:feat/generate-codeowners-output-dir-flag
Oct 16, 2024
Merged
feat: --output-path
flag for pizza generate codeowners
#223
nickytonline
merged 1 commit into
open-sauced:beta
from
udaypatel1:feat/generate-codeowners-output-dir-flag
Oct 16, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Compliance Checks Passed!
udaypatel1
changed the title
Feature: Add logic to handle output path flag for generating codeowners file
feat: add logic to handle output path flag for generating codeowners file
Oct 14, 2024
udaypatel1
changed the title
feat: add logic to handle output path flag for generating codeowners file
feat: Oct 14, 2024
--output-path
flag for pizza generate codeowners
jpmcb
requested changes
Oct 14, 2024
Great work on this! Thanks for taking the initiative to pick this up!! 👏🏼👏🏼 👏🏼 |
udaypatel1
force-pushed
the
feat/generate-codeowners-output-dir-flag
branch
2 times, most recently
from
October 15, 2024 14:18
0b30d66
to
a5a097f
Compare
jpmcb
requested changes
Oct 15, 2024
udaypatel1
force-pushed
the
feat/generate-codeowners-output-dir-flag
branch
3 times, most recently
from
October 15, 2024 18:39
b8d8a54
to
154a2d7
Compare
jpmcb
approved these changes
Oct 16, 2024
nickytonline
approved these changes
Oct 16, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this @udaypatel1! 🚢
udaypatel1
force-pushed
the
feat/generate-codeowners-output-dir-flag
branch
from
October 16, 2024 16:40
154a2d7
to
09ed80b
Compare
open-sauced bot
pushed a commit
that referenced
this pull request
Oct 16, 2024
## [2.4.0-beta.1](v2.3.0...v2.4.0-beta.1) (2024-10-16) ### 🍕 Features * `--output-path` flag for `pizza generate codeowners` ([#223](#223)) ([1c5ce09](1c5ce09))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds logic to handle an optional output directory flag value to the
generate codeowners
commandMirrors the expected behavior of the same flag that exists for
generate config
Related Tickets & Documents
Resolves #222
I am not sure how to self-assign the ticket – if an admin could assign the Issue to me, that'd be wonderful :)
Mobile & Desktop Screenshots/Recordings
Steps to QA
pizza generate codeowners
with and without the-o
/--output-path
flagpizza generate codeowners .
pizza generate codeowners . -o /path/to/some/directory/
pizza generate codeowners . -o /path/to/some/directory/ --owners-style-file
All other functionalities should remain unchanged and BAU. The optional flag should just create or modify in a specified file path that is given.
Tier (staff will fill in)
[optional] What gif best describes this PR or how it makes you feel?
Please let me know if I'm missing anything or there are complications! Thank you! 😁