Remove outputting md files to AppVeyor artifacts#16736
Conversation
WalkthroughThe recent updates streamline documentation and styling, focusing on removing outdated commands and refining styles for better compatibility. The Changes
Recent review detailsConfiguration used: .coderabbit.yml Files selected for processing (3)
Files skipped from review due to trivial changes (2)
Additional context usedPath-based instructions (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Link to issue number:
None
Summary of the issue:
Previously, markdown files were built as an intermittent step between converting text2tags content to HTML.
During this period, it was useful for builds to upload their markdown files as AppVeyor artifacts in the builds system.
We have now removed the t2t content in favour of a markdown source of truth, meaning that the artifact uploaded should be the same as the contents in the PR.
Description of user facing changes
Remove userGuide and changes markdown files from build artifacts
Description of development approach
Remove userGuide and changes markdown files from build artifacts
Also removed other deprecated code and updated remaining references to t2t
Testing strategy:
Test build results
Known issues with pull request:
Code Review Checklist:
Summary by CodeRabbit
Bug Fixes
Documentation
Refactor
TITLEandSETTINGS_SECTIONcommands for better readability and maintainability.