Rinkta + GitHub: closed issues and merged PRs become hours | Rinkta [Rinkta](https://rinkta.com/) Products Agencies Resources [Customers](https://rinkta.com/case-studies) [Pricing](https://rinkta.com/pricing) [Log in](https://app.rinkta.com/session/new) [Sign up for free](https://app.rinkta.com/registration/new) 1. [Home](https://rinkta.com/)/ 3. [Integrations](https://rinkta.com/integrations) # GitHub Closed GitHub issues and merged PRs become billable hours. Rinkta's AI reads what shipped, estimates time, and logs entries automatically. ## Overview Rinkta's GitHub integration captures billable work automatically when issues are closed or pull requests are merged. AI reads task descriptions, estimates completion time, and generates billing entries in real time. Your development work gets documented and turned into a billing entry without you lifting a finger. Development teams ship code. Rinkta handles the timesheet. ## How it works Connect your GitHub workspace to Rinkta in one click. Select your workspace, authorize the connection, and Rinkta starts monitoring your repositories. As your team closes issues and merges pull requests, Rinkta's AI reads the issue to understand what was actually done. It estimates how long the work took based on scope and complexity, then instantly creates a time entry and links it to the right project and client. The estimate is based on the work itself, not guesswork or hour blocks you vaguely remember. If it's off, adjust it in Rinkta. Everything else is already done. Before you connect GitHub, set up your clients and projects in Rinkta. Once you map repositories to projects, completed work gets logged to the correct client automatically. No tags, no manual sorting, no late night detective work trying to figure out which repo was for which client. ## Configure Workspace administrators authenticate via OAuth2 in Rinkta settings. Select the GitHub organization or user account to connect, grant repository permissions, and Rinkta registers webhook endpoints for issues and pull_requests events. Webhooks listen for closed issue events and closed pull request events with merged status. Upon trigger, AI processes the issue body or PR description to generate time estimates logged against mapped Rinkta projects. Map repositories to projects at the workspace level to route completed work to client accounts. Webhook payloads process in real-time, creating entries immediately after closure or merge. GitHub ---
Website
[https://github.com ](https://github.com)
Documentation
[https://docs.github.com ](https://docs.github.com)
--- [Add to Rinkta](https://app.rinkta.com/registration/new) FAQ ## GitHub integration FAQ Common questions about turning closed GitHub issues and merged pull requests into billable hours with Rinkta.
Can I track billable hours from closed GitHub issues and merged pull requests? ◀ Yes. Rinkta's GitHub integration logs hours when issues are closed or pull requests are merged. AI reads the issue body or PR description, estimates how long the work took based on scope, and creates a billing entry against the right repository and client. There's no manual GitHub time tracking and no timesheet.
---
How does Rinkta capture work from GitHub? ◀ GitHub webhooks fire on closed issues and on pull requests merged to the default branch. AI parses the issue body or PR description, calculates a time estimate from the scope of the change, and posts a billing entry to the Rinkta project mapped to that repository.
---
What permissions does the GitHub integration need? ◀ Setup uses OAuth2 and asks for read access to issues and pull requests on the repositories you select. Rinkta registers webhook endpoints for the issues and pull_request events. No write access to your GitHub repositories is needed.
---
Does the GitHub integration work for client agencies and dev teams? ◀ Both. Client agencies map per-client repositories to Rinkta projects so merged PRs and closed issues route to the right invoice. Internal dev teams map their delivery repos for accurate per-project hour reporting. Either way, shipped code becomes billable hours automatically.
---
How accurate are AI time estimates from GitHub PRs and issues? ◀ Estimates come from what the issue or PR describes — the body, the scope of the change, and the linked work. Adjust the estimate in Rinkta if it looks off for a given PR. Most teams find the AI close enough that they only edit outliers, which is faster than asking developers to log hours.
---
How is this different from manually tracking developer hours? ◀ Manual time tracking asks engineers to stop coding, remember what they worked on, and enter hours. Rinkta's GitHub integration captures hours from work that's already been merged — no timer, no estimation meeting, no Friday afternoon timesheet scramble. Hours land in the invoice as code ships.
### Try it risk-free for a week Here's the deal. Use it free for 7 days. If you don't save at least a couple hours or find work you should have billed, we'll refund everything. No questions, no hassle. [Sign up for a free trial](https://rinkta.com/registrations/new) No credit card required [Rinkta](https://rinkta.com/) Automatic billable hours and one-click invoicing for agencies. Built so your team can stop chasing timesheets. ### Product - [Time tracking](https://rinkta.com/products/time-tracking) - [Insights](https://rinkta.com/products/insights) - [Invoices](https://rinkta.com/products/invoices) - [Integrations](https://rinkta.com/integrations) - [Pricing](https://rinkta.com/pricing) - [MCP](https://rinkta.com/mcp) ### Solutions - [Software agencies](https://rinkta.com/agencies/software) - [Creative agencies](https://rinkta.com/agencies/creative) ### Resources - [Guides](https://rinkta.com/guides) - [Customer stories](https://rinkta.com/case-studies) - [Profitability calculator](https://rinkta.com/resources/calculators/profitability-calculator) - [Utilization calculator](https://rinkta.com/resources/calculators/utilization-calculator) - [Alternatives](https://rinkta.com/alternatives) ### Company - [About](https://rinkta.com/about) - [Contact](https://rinkta.com/contact) - [Security](https://rinkta.com/security) ## Subscribe to product updates One short email a month. New features, what we shipped, and lessons from running an agency on Rinkta. Email © 2026 Rinkta. All rights reserved. • Developed, shaped, and backed by [ Primevise](https://primevise.com/?ref=rinkta) - [Discord](https://rinkta.com/join/discord) - [X / Twitter](https://x.com/rinktacom) - [LinkedIn](https://www.linkedin.com/company/rinkta) - [Instagram](https://www.instagram.com/rinktacom/) - [Facebook](https://www.facebook.com/rinktacom) - [Privacy Policy](https://rinkta.com/privacy-policy) - [Terms of Service](https://rinkta.com/terms-of-service)