-
-
Notifications
You must be signed in to change notification settings - Fork 636
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
Add ruff, adjust pyugprade, autoflake in docs #19555
Conversation
I tried to automatically cherry-pick this change back to each relevant milestone, so that it is available in those older releases of Pants. ❌ 2.16.xI was unable to cherry-pick this PR to 2.16.x, likely due to merge-conflicts. Steps to Cherry-Pick locallyTo resolve:
Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary. ❌ 2.17.xI was unable to cherry-pick this PR to 2.17.x, likely due to merge-conflicts. Steps to Cherry-Pick locallyTo resolve:
Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary. When you're done manually cherry-picking, please remove the Thanks again for your contributions! |
Fixes pantsbuild#19273 by adding ruff to the docs, both the auto-generated backend docs and the manual pages that list out backends. This doesn't try to solve the general problem of reminding us to add backends to docs. While I was there, I noticed the pyupgrade and autoflake backends were referring to the `experimental` paths, but they've now graduated to non-experimental, so this switches them over.
Fixes pantsbuild#19273 by adding ruff to the docs, both the auto-generated backend docs and the manual pages that list out backends. This doesn't try to solve the general problem of reminding us to add backends to docs. While I was there, I noticed the pyupgrade and autoflake backends were referring to the `experimental` paths, but they've now graduated to non-experimental, so this switches them over.
…#19576) Fixes #19273 by adding ruff to the docs, both the auto-generated backend docs and the manual pages that list out backends. This doesn't try to solve the general problem of reminding us to add backends to docs. While I was there, I noticed the pyupgrade and autoflake backends were referring to the `experimental` paths, but they've now graduated to non-experimental, so this switches them over.
…#19577) Fixes #19273 by adding ruff to the docs, both the auto-generated backend docs and the manual pages that list out backends. This doesn't try to solve the general problem of reminding us to add backends to docs. While I was there, I noticed the pyupgrade and autoflake backends were referring to the `experimental` paths, but they've now graduated to non-experimental, so this switches them over.
Fixes #19273 by adding ruff to the docs, both the auto-generated backend docs and the manual pages that list out backends. This doesn't try to solve the general problem of reminding us to add backends to docs.
While I was there, I noticed the pyupgrade and autoflake backends were referring to the
experimental
paths, but they've now graduated to non-experimental, so this switches them over.