-
-
Notifications
You must be signed in to change notification settings - Fork 10
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: pizza generate insight
command
#179
Conversation
Signed-off-by: John McBride <[email protected]>
342ff57
to
235d883
Compare
The command works good for me. How does this handle attribution groups vs usernames? If I have an |
It doesn't. It just uses a regex to look for the The For example, this request to the API:
throws out the two logins that aren't actually logins. Abit of a rough experience. In the future we could hit the |
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.
🚢
## [1.5.0](v1.4.0...v1.5.0) (2024-09-16) ### 🐛 Bug Fixes * Config path prefers local dir vs. home dir ([#184](#184)) ([859446a](859446a)) * Don't overwrite ldflags in justfile builds ([#171](#171)) ([e024687](e024687)) ### 🍕 Features * Cut 2.0.0 release ([#193](#193)) ([278a833](278a833)) * pizza generate insight command ([#179](#179)) ([7315a1d](7315a1d)) * Update README docs ([#186](#186)) ([99328aa](99328aa))
Description
Refactors the existing interactive flow from
pizza generate codeowners
(after the codeowners file has been created) into its own command:Related Tickets & Documents
Closes #176
Steps to QA
just build
./build/pizza generate insight .
in a directory with aCODEOWNERS
fileTier (staff will fill in)