Update "Writing lock file" placement #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I just realized that this PR must be applied only after next release. So, I'm putting as a draft until it happens. |
wagnerluis1982
force-pushed
the
update-writing-lock-file-output
branch
from
b9e4e0f to
1ab3451
Compare
|
Since 1.5 was released, I guess this change to the front page |
|
Deploy preview for website ready! ✅ Preview Built with commit 1ab3451. |
radoering
approved these changes
May 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After python-poetry/poetry#7498, the output "Writing lock file" is now at the end of
poetry addcommand.This PR updates the output displayed in the front page https://python-poetry.org/
Screenshot (with the change)