MAINT: Phase 1 - Add HTML archives to GitHub release assets#15
Merged
Conversation
- Translate functions.md from English to Persian - Update _toc.yml to include functions lecture - Maintain all code examples and technical syntax - Preserve right-to-left (RTL) formatting for Persian text
- Changed from treating warnings as errors to allowing warnings - This enables preview builds to complete successfully - Kept -n (nitpick) and --keep-going flags for better error reporting
Implements Phase 1: HTML archive backup on releases.
## Changes
This commit adds steps to the publish.yml workflow to create and upload HTML archives as GitHub release assets:
1. Create HTML archive - Compresses _build/html/ into a .tar.gz archive after the HTML build
2. Generate checksum - Creates SHA256 hash for integrity verification (html-checksum.txt)
3. Create manifest - Generates metadata file with build information (html-manifest.json)
4. Upload to release - Attaches all three files to the GitHub release using softprops/action-gh-release@v1
## Release Assets Created
Each publish-* tag will now include:
• 📦 lecture-python-programming-fa-html-{tag}.tar.gz - Full HTML site archive
• 🔐 html-checksum.txt - SHA256 verification file
• 📋 html-manifest.json - Build metadata (tag, commit, timestamp, size, file count)
## Key Features
• ✅ Does not modify _build/html/ directory (gh-pages deployment unaffected)
• ✅ Preserves existing release notes (no body override)
• ✅ Automatic tag detection from workflow context
• ✅ Creates safety net before Phase 2 (gh-pages history cleanup)
✅ Deploy Preview for majestic-griffin-10b166 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Implements Phase 1 from the publishing workflow upgrade: HTML archive backup on releases.
Changes
This PR adds steps to the
publish.ymlworkflow to create and upload HTML archives as GitHub release assets:_build/html/into a.tar.gzarchive after the HTML buildhtml-checksum.txt)html-manifest.json)softprops/action-gh-release@v1Release Assets Created
Each
publish-*tag will now include:• 📦
lecture-python-programming-fa-html-{tag}.tar.gz- Full HTML site archive (~200-300 MB)• 🔐
html-checksum.txt- SHA256 verification file• 📋
html-manifest.json- Build metadata (tag, commit, timestamp, size, file count)Key Features
• ✅ Does not modify
_build/html/directory (gh-pages deployment unaffected)• ✅ Preserves existing release notes (no
bodyoverride)• ✅ Automatic tag detection from workflow context
• ✅ Creates safety net before Phase 2 (gh-pages history cleanup)
Testing Plan
After merge, test with a
publish-test-*tag to verify:sha256sum -c html-checksum.txtRelated
meta/publishing-workflow-upgrade-tracking.md