Cost where the ticket already lives
Whoever opens the issue sees the running total in the thread. They get the answer to "what has this cost so far" without leaving GitHub or opening a dashboard.
Issue tracking
Post the AI cost of an issue as a comment on the issue itself.
Lineman posts the AI cost of a piece of work as a comment on the GitHub issue it belongs to, and edits that comment in place as the figure moves. Whoever is reading the ticket sees what it has cost so far, in US dollars, without opening Lineman. Lineman reads the issue reference out of the branch name or the commit message, so nothing is logged by hand. There is nothing new to connect: issue comments reuse the Lineman GitHub App you already installed for cost attribution, and Lineman comments only on issues in repositories that App can see.
Whoever opens the issue sees the running total in the thread. They get the answer to "what has this cost so far" without leaving GitHub or opening a dashboard.
Write the reference as #123, either in the branch name (fix/#123-retry-timeout) or in the commit message, and the spend attaches to that issue. The # is required. A bare 123 is not matched, because branch names are full of dates, versions and ticket ids from other trackers. Work that never mentions an issue is still costed in Cost Explorer, it is just not attached to a ticket.
Lineman posts a single comment per issue and edits that same comment as the total changes, rather than adding a new one on every update. The figure is the cumulative total for that issue in that repository. Do not edit or delete the comment: Lineman recognises its own comment by a marker in the body, and without that marker the next update posts a second comment.
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideEvery integration in one place, searchable by name and filterable by what it does.
View all integrations