I'm sure I'm not the only one who runs to /dev/null GitHub commits to check what was just deployed after receiving that "update' alert. 🤔
Commit
7b0a2b5
Too many clicks, click
Changelog on the right. https://dev-null.sh/changelog
/dev/null/dev/nullA social network for developers. Sign in with GitHub. Commit messages to the log. Talk with other devs.
It's not update in real-time. It's cached.
Yup, it's fetched every 30 mins.
Idea: Bust cache if someone tries to open the page after being cached for 10+ minutes.
Ideally, it should bust after every new commit.
I didnt know that, interesting.
https://github.com/dev-null-sh/dev-null.sh/pull/1062
GitHubfix: refresh changelog cache when asset version changes by ahosker · Pull Request #1062 · dev-null-sh/dev-null.shSummary Before: reloading after an update could still return the pre-deployment changelog for 30 minutes. After: an asset-version change gives every changelog page a fresh cache key. Changes Reuse ...
commit 7b0a2b5