PRs excluded from publication via GitHub label
Merged PRs cluttering the timeline? Gitpulse now reads a \"gitpulse:ignore\" label from GitHub and automatically drops those stories from the publication — retroactively and on demand.
Merged PRs that land in the timeline by mistake, or PRs that shouldn't be publicized, previously required manual cleanup. Gitpulse now recognizes a gitpulse:ignore label on merged PRs and excludes them from the publication entirely.
Applying the label removes the PR's story from the next analyzer run. The implementation handles two edge cases: PRs labeled after the analyzer already swept through them, and PRs labeled between the sweep and the per-commit fetch. Removing the label re-publishes the story, as long as the merge commit still falls within the configured bootstrap window.
The label name is configurable. Teams can use any label they prefer by setting labels.ignore in .gitpulse.json — the default is gitpulse:ignore. The configuration schema is designed to accommodate future label-based actions without requiring another schema migration.
This change lives in the gitpulse CLI analyzer. It adds 350 lines across 9 files, including a new GraphQL search function for label discovery and a sweep that cleans up previously-generated story files.