Once a project is analysed, Specsight keeps the spec current on its own. Every release on the watched branch triggers a sync that updates only the scenarios affected by the change. The rest of the spec is left alone.
How it works
- A release lands on the watched branch
- GitHub sends Specsight the change set
- Specsight identifies which features are affected and re-reads those areas of the code
- Affected scenarios are added, updated, or removed
- The change lands in the changelog with before-and-after values
What you see while it runs
The spec stays fully readable during a sync. A banner appears on the project page while it runs; the Recent activity card and open feature pages refresh when it finishes.
Specsight also sends a sync notification — an in-app bell entry for every Member, and an email to Members who have Sync complete turned on in their notification settings.
Limits
Every plan has the same monthly sync allowance — see plans and limits. Syncs that exceed the cap are skipped, and the spec stays at the last successful sync until the next billing cycle or an upgrade.