Back to all integrations

Source control

Lineman and GitHub

Attribute spend to repositories and branches, and choose which repositories Lineman is allowed to see.

What this gets you

Lineman attributes AI coding spend to the repository and branch it came from, so Cost Explorer can show spend per repository and per branch. You tick the repositories your team is expected to work in, and spend on any repository you did not tick is flagged. The GitHub App reads repository and branch metadata only, so there is nothing to add to individual repos.

What people use it for

  • Cost per repository and branch

    Cost Explorer breaks AI spend down by repository and by branch. Lineman discovers the repositories the GitHub App can see, along with their branch conventions, so the breakdown appears without any per-repo configuration.

  • Flag spend outside authorised repos

    Tick the repositories your team is expected to work in, or use Authorise all if every discovered repository is fair game. Spend on any unticked repository, such as a personal fork or a repository outside the team, is flagged so it stands out.

  • New repos picked up automatically

    Lineman re-syncs periodically, so repositories and branches added after you connect are picked up without reconnecting. If you change the App's repository access in GitHub, press Sync to re-discover them.

More in Source control

Set up GitHub

The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.

Read the setup guide

Looking for something else?

Every integration in one place, searchable by name and filterable by what it does.

View all integrations