Repository navigation
PEP 696: Have Discussions-To point to thread rather than comment - #3053
Merged
CAM-Gerlach merged 1 commit intoMar 12, 2023
Merged
Conversation
JelleZijlstra
approved these changes
Mar 12, 2023
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
2 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.
PEP 123: Summary of changes)PR #3052 accidentally linked directly to an arbitrary comment in the Discussions-To thread rather than the thread itself, and managed to bypass the linter by adding a trailing slash, which was introduced in #3005 as an escape hatch in response to the author's desire in #3004 to link to a specific post, given a strong reason to do so. It was presumably unintentional here, and thus this PR fixes it.
📚 Documentation preview 📚: https://pep-previews--3053.org.readthedocs.build/