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: 🎸 Create safeguard when running generate in existing pkg #249

Merged
merged 1 commit into from
Jun 8, 2024

Conversation

abelsiqueira
Copy link
Owner

If generate is run in a path that has an answer file, a warning message
is shown to remind the user of the update command.

✅ Closes: #247

Copy link

codecov bot commented Jun 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (5d0d6e6) to head (12169b2).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #249   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           53        57    +4     
=========================================
+ Hits            53        57    +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

If generate is run in a path that has an answer file, a warning message
is shown to remind the user of the update command.

✅ Closes: #247
@abelsiqueira abelsiqueira merged commit 045a5da into main Jun 8, 2024
7 checks passed
@abelsiqueira abelsiqueira deleted the 247-safeguard branch June 8, 2024 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Create safeguard against generate being run instead of update
1 participant