Removes the nightly test build (schedule 15 3 * * *) from the workflow and the references to it.
.gitea/workflows/continuous_integration.yaml: schedule trigger removed; the schedule conditions in build-test, deploy-test and lighthouse removed. push to master, pull_request and workflow_dispatch stay.
docs: deploy-and-ci.md (triggers table, new section), cms-integration.md, go-live-checklist.md, README.md. A content change needs no rebuild (NFR-10); production gets the same only when the ASF production site is served by the CMS host (IIS pipeline, later).
Why: the CMS host now writes packages, banners and the hero into the first HTML of every request, and the nightly run put master over ASF-test every night.
Not in this PR: OFFERINGS_URL and VITE_SITE_URL in build-test stay (separate follow-up).
Schedules only run from the default branch, so this works only once it is merged. Do not merge without Bryan's explicit go.
Removes the nightly test build (schedule 15 3 * * *) from the workflow and the references to it.
- .gitea/workflows/continuous_integration.yaml: schedule trigger removed; the schedule conditions in build-test, deploy-test and lighthouse removed. push to master, pull_request and workflow_dispatch stay.
- docs: deploy-and-ci.md (triggers table, new section), cms-integration.md, go-live-checklist.md, README.md. A content change needs no rebuild (NFR-10); production gets the same only when the ASF production site is served by the CMS host (IIS pipeline, later).
Why: the CMS host now writes packages, banners and the hero into the first HTML of every request, and the nightly run put master over ASF-test every night.
Not in this PR: OFFERINGS_URL and VITE_SITE_URL in build-test stay (separate follow-up).
Schedules only run from the default branch, so this works only once it is merged. Do not merge without Bryan's explicit go.
The schedule trigger and its conditions in the jobs are gone; docs say that a
content change needs no rebuild (NFR-10) and that production gets the same
only once it is served by the CMS host.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Removes the nightly test build (schedule 15 3 * * *) from the workflow and the references to it.
Why: the CMS host now writes packages, banners and the hero into the first HTML of every request, and the nightly run put master over ASF-test every night.
Not in this PR: OFFERINGS_URL and VITE_SITE_URL in build-test stay (separate follow-up).
Schedules only run from the default branch, so this works only once it is merged. Do not merge without Bryan's explicit go.