Add "planned" status for pre-branch version#329
Merged
Conversation
StanFromIreland
approved these changes
Mar 7, 2026
Contributor
|
Doesn't it make us try to build docs for an empty branch name now? If so, we should skip it verbosely, or add a check for the branch. |
Member
Author
|
You're right! Would you like to open a PR? Thanks! |
Member
Author
|
I've opened #330. |
Contributor
|
Thank you for opening the PR and sorry I didn't do that. I had troubles reproducing the issue locally, and this week is exceptionally busy for me. |
Member
Author
|
No problem, thanks for the review! |
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.
To avoid logging warnings when we merge python/peps#4853.