Gitpulse self-deploy switched to event-driven triggers
Gitpulse's own deployment pipeline abandons daily cron for push and release triggers—no more idle runs, new content appears within minutes.
The GitHub Actions self-deploy workflow no longer runs on a fixed schedule. Instead, it fires on pushes to main and published releases. Documentation now gives consumers a choice: an event-driven option that reflects new content quickly, or a daily cron for lower CI footprint on sporadic repos.
Installing Gitpulse? The README walks through both options side by side with clear tradeoffs. Option A (now recommended) uses push + release + manual triggers—re-publishes the moment something lands. Option B sticks with a daily 09:00 UTC run plus manual trigger for repos with infrequent activity. Both snippets are copy-paste ready, and switching between them is a single YAML edit away.
In the site package, a build script picked up a --webpack flag via CodeRabbit auto-fix. The main repo's content update loop is now tightly coupled to actual activity rather than time.