Gitpulse deployment goes event-driven
Gitpulse's self-deploy workflow now triggers on GitHub push and release events instead of a daily cron, cutting idle CI runs while keeping content fresh within minutes of any change.
Gitpulse's GitHub Actions deployment workflow no longer runs on a fixed 09:00 UTC schedule. Instead, it triggers the moment new commits land on main or a release is published — whichever comes first. Content updates appear within a couple of minutes rather than waiting up to a day.
The README now offers two installation cadences for consumers to pick from. Option A (event-driven) runs on every push and release, with no scheduled downtime between updates. Option B (daily) keeps the cron schedule for repos with sporadic activity where minimizing CI footprint matters more than freshness. Both are copy-paste ready and swappable — users can edit their workflow file later to switch between them.
The project's own site deploys under Option A, while users cloning the workflow get to choose their own tradeoff. A minor build adjustment in site/package.json adds a webpack flag to the Next.js build command to support the refactor.