-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Fix syntax errors/warnings in 6.4 #21614
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
Conversation
| in the development branch. | ||
| * **Bug**: Only for bug fixes; We are very conservative when it comes to | ||
| merging older, but still maintained, branches. Read the :doc:`maintenance` | ||
| merging older, but still maintained, branches. Read the :doc:`/contributing/code/maintenance` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@OskarStark this might be an interesting one for DOCtor when you have time: we want all doc references to be absolute paths, so the links don't break when moving documents/sections. This has been a rule since forever, but every once in a while one relative path slips in :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I created an issue for DOCtor
|
Thank you @wouterj. |
…path` rule (OskarStark) This PR was squashed before being merged into the 6.4 branch. Discussion ---------- Update DOCtor-RST to 1.77.0 and enable `no_relative_doc_path` rule - Require DOCtor-RST 1.77.0 - Enable `no_relative_doc_path` rule to ensure `:doc:` directives use absolute paths ### Refs * #21614 (comment) `@wouterj` * OskarStark/doctor-rst#2180 * OskarStark/doctor-rst#2213 I will take care of the upmerge and fixing the other issues in the upper branches, once approved. Commits ------- 67506ba Update DOCtor-RST to 1.77.0 and enable `no_relative_doc_path` rule
Some syntax warnings found by the phpDocument parser that were introduced in the past year.
I'll see if I can maybe add a new CI job with the new parser, which is a lot more detailed about syntax mistakes. That'll help us prepare for the migration.