You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prevent deploying the same docs when nothing has changed
Use GitHub Action caching mechanism to store the last built versions,
keyed using both this repo's and MacVim's commit. This prevents us from
unnecessarily re-generating the page every day and help with browser
caching behaviors. We still build the page regardless as it finishes
quickly and good for sanity checking that nothing broke.
We do allow manual workflow dispatch to always deploy, since that's a
manual action that indicates we want to do so.
Copy file name to clipboardExpand all lines: notes/Design_Notes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,4 +17,4 @@ vimhelp was modified to export a tags.json file during build. This file embeds a
17
17
18
18
Publish the documentation using GitHub pages for simplicity and so we don't have to run a server. Since everything is generated by vimhelp, we don't really need an intermediate step of pushing to a gh-pages branch first. Instead, GitHub has a newer feature that allows us to directly publish the page as an artifact and deploy from it, thus saving us from having to push to a gh-pages branch, which would actually have bogged down the repo by storing useless history.
19
19
20
-
Currently it's configured to run nightly as of this writing. Ideally we have a way to check whether any change has actually happeed at the MacVim repo but that would require finding some way to store a persistent state in CI, or store a JSON file in the published page that we could query (for the last built commit). Since the whole thing finishes in like 1 minute, there really isn't a pressing need to do so.
20
+
Currently it's configured to run nightly as of this writing, but it will only deploy the page if something has changed (otherwise it will just build the artifact but does not deploy it) to help preserve browser caching.
0 commit comments