Integration · GitHub

Turn merged pull requests into updates your client can follow.

Connect a repository and every merged pull request lands in a private inbox on your project. Reword it, publish the ones that matter, and your client gets a timestamped record of the work, without a GitHub account or access to your code.

How the GitHub integration works

Set it up once per project. After that, your merged work comes to you instead of you writing updates from memory.

  1. 01

    Install the GitHub app

    Install ClearTimeline on your account or an organisation and choose which repositories it can see. It asks for read access to pull requests and repository metadata, nothing else.

  2. 02

    Link a repository

    On the project's Settings tab, pick the repository that holds the client's work. A project can follow more than one repository.

  3. 03

    Review what was merged

    Each merged pull request appears in the From GitHub inbox on the Timeline tab, with its title and description as a draft. Only you can see it.

  4. 04

    Publish for your client

    Rewrite it in plain language, choose delivery, milestone or note, and publish. Or dismiss it. Published entries are locked like every other entry.

From merge to sign-off, on one record

A freelance developer adds guest checkout to a client's store after a mid-project change request.

When the invoice includes the six extra hours, the request, the delivery and the approval are already on one timeline, in order.

  1. Tue 10 Mar 2026, 09:14 UTC

    Scope change logged: client asks for guest checkout, estimated at 6 extra hours.

  2. Thu 12 Mar 2026, 16:42 UTC

    Pull request #48 merged on GitHub. It waits in your private inbox.

  3. Thu 12 Mar 2026, 17:05 UTC

    Published as a delivery: “Guest checkout is live on staging”, with the pull request link and merge time as its source.

  4. Fri 13 Mar 2026, 08:31 UTC

    Client opens the project portal and views the update.

  5. Fri 13 Mar 2026, 10:12 UTC

    Client approves guest checkout from the approval link.

Why not just share the repository?

GitHub is the right place for the code. It's a poor place for a non-technical client to follow progress.

  • Your client needs a GitHub account and access to your code

    Your client opens a private link. No account, no code

  • Commit messages and pull requests are written for developers

    You reword each update in plain language before your client sees it

  • Every small fix and work-in-progress branch is visible

    Only merged pull requests arrive, and only the ones you publish are shown

  • Code changes sit apart from what the client agreed to

    Updates sit next to the agreed scope, change requests and approvals

  • No record of whether the client looked

    The portal records when your client views the latest work

What the integration can and can't do

The point of the record is that your client can trust it, so the integration asks for as little as possible.

  • Pull request details only

    Two read-only permissions: pull requests and repository metadata. ClearTimeline doesn't request access to repository contents and never reads your code.

  • Nothing publishes on its own

    Merged pull requests wait in a private inbox. Your client only sees what you choose to publish.

  • A source line that can't be faked

    Each published entry ends with the pull request number, repository, merge time in UTC and a link, added by the server. Entries you write by hand can't carry the GitHub label.

  • Never backdated

    An entry is timestamped when you publish it. The original merge time stays in its source line, so the record shows both.

  • Personal and organisation repositories

    Install it on your own account or a GitHub organisation, and choose which repositories, public or private, it can see.

  • Unlink any time

    Unlink a repository and new pull requests stop arriving. Updates you already published stay on the timeline.

Built for developers who bill clients

Most freelance developers already describe their work well, in pull request titles and descriptions. The problem is that clients never see it, so progress updates get written from memory on a Friday afternoon, or not at all.

The GitHub integration reuses what you already wrote. It doesn't summarise, guess or add claims of its own: the draft is your pull request title and description, and you decide what your client reads.

  • Freelance web and app developers sending weekly progress updates
  • Small agencies whose clients don't use GitHub
  • Retainers where the client wants to see what the hours went on
  • Fixed-price projects where scope changes need a paper trail

Questions

Does my client need a GitHub account?

No. Your client opens the project portal from a private link, with no sign-up. They see the updates you published, not your repository.

Can ClearTimeline see my code?

No. The GitHub app asks for read access to pull requests and repository metadata only. It doesn't request access to repository contents, and it only reads pull request details such as the title, description, number, author and merge time.

Which GitHub events are supported?

Merged pull requests. Commits, pushes, issues and releases aren't imported. Releases would need read access to repository contents, which ClearTimeline deliberately doesn't ask for.

Do merged pull requests appear on my client's timeline automatically?

No. They land in a private inbox on the project's Timeline tab. You publish the ones your client should see and dismiss the rest.

Can I edit a pull request before publishing it?

Yes. You can change the title and text and choose the entry type. Once published, the entry is locked: it can't be edited or deleted, like every ClearTimeline entry.

Does it work with GitHub organisations?

Yes. If you're not an owner of the organisation, GitHub sends your install request to an owner. Once they approve it, connect again from the project's Settings tab.

Is the GitHub integration included in the free plan?

Yes, on both plans. On the free plan, published GitHub updates count toward the limit of 10 updates per project. Professional is $10 a month for unlimited projects and updates.

What happens if I unlink a repository?

New merged pull requests stop arriving and any waiting in the inbox are removed. Updates you already published stay on the timeline.

Show clients the work behind the invoice

Connect a repository and publish your first update in a few minutes. ClearTimeline is free for 1 project, no credit card needed.

Free forever for 1 project
No credit card required