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

Handle no pyproject file in migration #100

Merged
merged 1 commit into from Dec 10, 2022
Merged

Conversation

blink1073
Copy link
Member

Fixes #87

@blink1073 blink1073 added the bug Something isn't working label Dec 10, 2022
@codecov
Copy link

codecov bot commented Dec 10, 2022

Codecov Report

Base: 92.20% // Head: 92.20% // No change to project coverage 👍

Coverage data is based on head (5b3c660) compared to base (b743974).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #100   +/-   ##
=======================================
  Coverage   92.20%   92.20%           
=======================================
  Files           5        5           
  Lines         218      218           
  Branches       56       56           
=======================================
  Hits          201      201           
  Misses         12       12           
  Partials        5        5           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@blink1073 blink1073 merged commit bf1e5c4 into main Dec 10, 2022
@blink1073 blink1073 deleted the fix-migration-no-pyproject branch December 10, 2022 23:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migration script fails if the project doesn't have a pyproject.toml yet
1 participant