Move PDF generation to dedicated VM and unify documentation publishing #131
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.
🎯 Objective
Optimize documentation publishing by moving PDF generation to dedicated virtual machines and unifying the documentation publishing process as requested in #59.
📋 Issue Reference
Fixes #59
🚀 Implementation
1. PDF Generation Optimization
pdf-generationlabel2. Unified Documentation Publishing
3. Script Unification
.scripts/publish-unified-docs.shfor unified documentation publishing🔄 Workflow Changes
Before:
After:
📁 Files Changed
.github/workflows/csharp.yml: Updated workflow to use dedicated VM and artifacts.scripts/publish-unified-docs.sh: New unified documentation publishing script🖥️ Self-Hosted Runner Requirements
For optimal performance, self-hosted runners with the
pdf-generationlabel should have:# LaTeX and dependencies pre-installed sudo apt-get install -y texlive texlive-lang-cyrillic texlive-latex-extra python-pygments ghostscript✅ Benefits
🧪 Testing
The implementation:
🤖 This PR was automatically generated to solve issue #59