CI/CD·Pushed May 1, 2026·XS
GitPulse self-deploys daily now
GitPulse is now running its own analyzer against itself every day at 09:00 UTC — practicing what it preaches by dogfooding the same workflow it sells to users.
GitPulse's self-deployment workflow now runs on a schedule — daily at 09:00 UTC — in addition to triggering on pushes and manual dispatch. The workflow runs GitPulse's own analyzer on the [[code]]znat/gitpulse[[/code]] repository, a practice known as "dogfooding" where a product is used to analyze itself. This ensures the team receives regular automated insights into their own codebase, catching issues on a consistent cadence rather than only when changes land. The workflow continues to trigger on pushes to main and via manual workflow dispatch, with the scheduled run providing an additional reliable heartbeat.
Technical description
The change modifies [[code ref=1]]self-deploy.yml[[/code]] to add a scheduled trigger alongside the existing push and workflow_dispatch triggers. A cron expression [[code]]0 9 * * *[[/code]] runs the workflow daily at 09:00 UTC.
A clarifying comment was added to the top of the file: "Runs the gitpulse analyzer on this repo (znat/gitpulse) — dogfooding the same reusable workflow that consumers will install on their own repos."
This establishes a consistent daily analysis cadence for the repository itself, ensuring GitPulse's team benefits from the same automated insights they offer customers. The workflow can still be triggered manually or on-demand via workflow_dispatch.
````yaml
file=.github/workflows/self-deploy.yml
on:
push:
branches: [main]
schedule:
# Daily at 09:00 UTC.
- cron: "0 9 * * *"
workflow_dispatch:
````
Files at a Glance:
- [[code]].github/workflows/self-deploy.yml[[/code]] — Added daily scheduled trigger at 09:00 UTC to the CI workflow