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

Feature: --range flag for pizza generate config #175

Closed
zeucapua opened this issue Sep 12, 2024 · 1 comment · Fixed by #218
Closed

Feature: --range flag for pizza generate config #175

zeucapua opened this issue Sep 12, 2024 · 1 comment · Fixed by #218

Comments

@zeucapua
Copy link
Contributor

zeucapua commented Sep 12, 2024

Suggested solution

Implement a new --range flag for the pizza generate config command to set how far back in time the program should look into when going through the repository's commit logs.

Context

Having an existing .sauced.yaml, it regenerated it, but the missing premable in comments got removed. Not sure if that's from our template, but just mentioning it.

When regenerating the .sauced.yaml, if one is detected (non-interactive mode) potentially mention it before they proceed.

Also, not sure how far back we're looking by default in the git history, but I see Anush, one of our interns in the list.

CleanShot 2024-09-10 at 13 50 41

Also, we should skip known bot accounts, i.e. any account ending in [bot].

Originally posted by @nickytonline in #137 (review)

Copy link
Contributor

open-sauced bot commented Oct 16, 2024

🎉 This issue has been resolved in version 2.4.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging a pull request may close this issue.

1 participant