-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
doc(faq): add entry for PEP 621 migration #9996
Conversation
Reviewer's Guide by SourceryThis pull request adds a comprehensive FAQ entry in the documentation to guide users on migrating their Poetry projects from the 'tools.poetry' section to the new 'project' section as outlined in PEP 621. It includes examples and notes on handling dynamic and static dependencies. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
Hey @abn - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 2 issues found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Deploy preview for website ready! ✅ Preview Built with commit 03006eb. |
0dd07b0
to
adb340c
Compare
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.
I like 👍 Just one minor thing.
adb340c
to
03006eb
Compare
Summary by Sourcery
Documentation:
tools.poetry
section to theproject
section inpyproject.toml
as per PEP 621.