-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
need to backport docathon PRs #8223
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
Comments
As mentionned on gitter, I feel uncomfortable backporting documentation pull request. We've identified a bug in the 2.0.0 documentation reference in a ticket (#8235), and if we backport the pull request that fixes this bug, we loose the information allowing to identify when the bug was discovered. |
(That's without considering the risk of backporting documentation that uses new features). |
Would backporting to |
The docathon has long gone, so I'm happy to port these all back to |
Great, these are all backported, thanks to everyone who did the original PRs, and sorry for the delay on my end... |
Thanks @dstansby. |
Rather than backporting each individual docathon PR, we will do one large docathon merge at the end of the week. Let's keep a list here of the docathon PRs that were accepted.
The text was updated successfully, but these errors were encountered: