Allow manually triggering production deployment#46
Merged
Conversation
This allows maintainers to optionally update the documentation as PRs are merged into other Poetry repos rather than needing to wait for the scheduled deployments.
neersighted
approved these changes
Jun 5, 2022
|
Deploy preview for website ready! ✅ Preview Built with commit 501689e. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This allows maintainers to optionally update the documentation as PRs are merged into other Poetry repos rather than needing to wait for the scheduled deployments. See the below screenshot for an example of this change in
mainof my fork.This is in response to python-poetry/poetry#4864. That issue related to the documentation on the website. The fix in Poetry's source (python-poetry/poetry#5771) was merged, but with the current cron-only website deployment there's a period of time where the issue has been closed but the site has not actually been updated.