Identity
GitHub can be a sign-in method without connecting repository data.
GitHub integration
Choose exactly which GitHub activity Shiptawk can review.
Connect selected repositories only when product changes should help Shiptawk prepare release marketing.
GitHub sign-in, App installation, repository selection, and monitoring opt-in are separate steps.
Connection boundary
Access is explicit at every stage.
Installation
The GitHub App connection establishes available repository access.
Selection
Only selected repositories can be associated with a product.
Monitoring
Shipping evidence begins only after an explicit repository opt-in.
Evidence used
Bounded repository context for product interpretation.
- Repository metadata
- Selected repository activity
- Commit and comparison context available to the integration
- Pull-request context where enabled
- Repository descriptions
- Bounded README context
What it does not do
Repository access is not permission to publish or surveil.
- Rank developers by activity
- Turn every commit into content
- Publish without approval
- Monitor repositories you did not select
- Treat private technical details as public facts
- Send unrestricted source payloads to an AI provider
Turn selected GitHub activity into useful growth evidence.
Separate source consent. Optional GitHub evidence. Approval before publication.