GitHub

Refund Rules

GitHub generally does not provide refunds for unused portions of monthly or annual subscriptions. However, they may provide prorated refunds in cases of billing errors or if you downgrade within the first billing cycle. Annual plans are typically non-refundable after the initial period. Credits may be issued for service outages or technical issues rather than cash refunds.

Credit Policies

GitHub provides service credits for significant downtime events that breach their SLA commitments (99.9% uptime for paid plans). Credits are typically calculated as a percentage of monthly fees based on downtime duration. They may also issue credits for billing errors or when customers are overcharged due to system issues. No credits are typically provided for unused seats or voluntary service reductions.

Contractual Terms

GitHub contracts typically include: (1) 30-day cancellation notice for annual plans, immediate for monthly; (2) Auto-renewal clauses that automatically renew subscriptions unless cancelled; (3) Price increase limitations - usually 30-60 days advance notice for material price changes; (4) Seat count changes take effect immediately for upgrades, at next billing cycle for downgrades; (5) Enterprise contracts may have custom termination clauses and volume discounts with minimum commitments.

Integration Complexity

Technical Notes

GitHub offers excellent REST and GraphQL APIs with comprehensive documentation. Authentication via Personal Access Tokens (PAT) or OAuth. Key considerations: (1) Rate limits of 5,000 requests/hour for authenticated requests; (2) GraphQL API uses cost-based query limits; (3) Organization billing APIs require admin-level permissions; (4) Audit log API only available for Enterprise plans; (5) Events API only retains 90 days of history; (6) Webhook support available for real-time updates. The Members API, Billing API, and Copilot API are well-documented and stable.