asc/cmba-bylaws
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

use summary-of-changes in release notes
All checks were successful
CI - Docs build check / build-check (push) Successful in 49s
Details
Build & publish docs (rc + release) / publish (push) Successful in 20s
Details

Browse Source
This commit is contained in:
Anthony Correa
2026-04-26 09:25:22 -05:00
parent f90ec3622e
commit 6c53b426bb
2 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -69,6 +69,8 @@ It builds both the normal site and an offline site package, then publishes based
- `rc*`: creates a GitHub prerelease, attaches the offline zip and generated `.docx`, and deploys the preview site to the `gh-pages` branch under `/rc/`
- `v*`: creates a GitHub release, attaches the offline zip, and deploys the release site to the root of the `gh-pages` branch
The GitHub release description is generated from `docs/summary-of-changes.md`. Draft and release-candidate prereleases prepend a short prerelease note before that summary.
In all cases, the release workflow uses the same MkDocs configuration in `mkdocs/mkdocs.yml`, with strict mode controlled by the `MKDOCS_STRICT` GitHub Actions variable.
## Project History