19 Commits
Author SHA1 Message Date
Lawrence Angrave 73a0f1e976 site_deploy: bump the _coursebook pointer instead of only nudging
The website consumes the wiki through the _coursebook submodule and
updates it with --remote, so the SHA recorded in the site's tree never
affects what deploys. It had drifted months behind as a result, which is
a trap for anyone who runs a plain 'git submodule update' and then builds
a stale book.

The trigger commit this script already pushes is the natural place to fix
that: point the gitlink at the wiki commit push_to_wiki.sh just published,
so the recorded pointer matches reality at no extra cost. ls-remote plus
update-index writes the gitlink directly, so the shallow clone never has
to fetch the submodule.

Both steps are non-fatal. The push is what rebuilds the site, and under
'set -e' a transient ls-remote failure would otherwise skip it. The commit
keeps --allow-empty so an already-current pointer still triggers a build.
2026-08-26 14:00:32 -05:00
Lawrence Angrave d6977dd170 Re-enable the website trigger using a deploy key
The coursebook now publishes its wiki again, but nothing tells the
website to rebuild, so a change reaches the site only when someone
else pushes to it.

Restore that trigger with a deploy key (SITE_DEPLOY_KEY) rather than
the built-in token: GITHUB_TOKEN is scoped to this repo, and pushes
made with it deliberately do not trigger workflows. A deploy key also
has no expiry and is exempt from the org's SAML SSO, so it will not
silently lapse the way the old credentials did.

- point site_deploy.sh at cs341-illinois/cs341-illinois.github.io; it
  still named illinois-cs241, two renames stale
- add IdentitiesOnly so ssh cannot offer some other key
- seed known_hosts with ssh-keyscan instead of relying on the runner
- skip the site deploy when the secret is absent, so forks still pass
2026-08-23 22:27:42 -05:00
Eric Zhang 8c49826577 Migrate to Github Actions (#184)
* Initial Github Actions workflow + script modifications

* Remove old keys

* Add deploy key

* Rename deploy key

* Oops add back

* Some changes after testing with website repo

* Remove env section

* Temporary changes for testing CI

* Enable github-actions on this branch for testing

* Fix?

* Only test out EPUB

* Fix?

* Fix?

* Update

* Typo and enable PDF

* Enable WIKI

* Add site deploy key

* Revert testing changes + Disable Github Actions on this branch

* Update README

* Typo

* Lowercase
2021-02-24 18:35:59 -08:00
bhuvy 13d88c97f8 Trying empty commit way of site building 2019-03-23 11:54:13 -05:00
bhuvy 82ada3415e Put in more documentation and comments 2019-03-13 11:14:38 -05:00
bhuvy d7752098cc Adding site deploy name change 2019-01-13 09:01:56 -06:00
bhuvy 0473d659e6 Fixing up probs 2018-12-17 14:36:22 -06:00
bhuvy e49908dfd6 sdf 2018-12-17 14:33:16 -06:00
bhuvy 6d3196f507 asdf" 2018-12-17 14:28:30 -06:00
bhuvy 7cd65c23f1 adf 2018-12-17 14:23:32 -06:00
bhuvy 5205b41cdc Debugging 2018-12-17 14:14:02 -06:00
Bhuvan Venkatesh 91515ad841 Update site_deploy.sh 2018-12-16 11:03:38 -06:00
Bhuvan Venkatesh 7caf47a53d Update site_deploy.sh 2018-12-16 10:57:08 -06:00
Bhuvan Venkatesh 964771a145 Update site_deploy.sh 2018-12-16 10:54:17 -06:00
Bhuvan Venkatesh 937ae9c692 Update site_deploy.sh 2018-12-16 10:50:38 -06:00
Bhuvan Venkatesh 21f880f29e One more level of fail safety 2018-11-21 20:14:49 -06:00
Bhuvan Venkatesh 2bb713a37e Safety plus specify before 2018-11-21 20:06:37 -06:00
Bhuvan Venkatesh 740fb07fe0 Too many ssh keys 2018-11-21 19:59:29 -06:00
Bhuvan Venkatesh a37f0873f4 Trying out autodeploys to the site 2018-11-21 19:54:17 -06:00