v1.8.0v1.9.0
Sign in with GitHub, agent spend that reaches the right ticket, and more
Sign in with GitHub
The sign-in page offers GitHub beside Google. Signing in with a provider joins your existing account only when the provider has verified that the email address is yours.
Agent spend reaches the right ticket
Several things could send an agent session's spend to the wrong ticket, or to no ticket at all. All of them are fixed.
- Repositories with capital letters in their name. For a repository whose GitHub name wasn't all lowercase, no agent session could be matched to its commits, so the whole project's agent spend landed in "No ticket". It's matched regardless of case now, and
clocktopus agent doctorstops reporting "no commits processed" for those repositories. - A commit made after the agent sat idle. An agent left idle overnight could commit in the morning before its next telemetry export arrived, and the commit was never linked. Clocktopus now checks again when the export lands.
- Pulls and merges. A session that pulled or merged claimed every commit that came with it, sometimes months of other people's work. A session's commits now come from the checkout's own history of what happened in it, so a pull or merge counts as nothing, and switching branches mid-session no longer drops the commits you'd already made there. Rebased commits don't count either.
- Forks. A session in a fork, whose
originis your own copy, couldn't be matched to the upstream repository the webhooks report. Every remote is checked now. - Sessions that crashed. A session closed after the agent died keeps the branch it was started on, rather than whatever branch the checkout was on hours later.
The fixes on your machine come with CLI 0.3.0. Update the CLI to get them.
One behaviour change: a checkout with two remotes attached to two different projects no longer goes to whichever remote is called origin. Its sessions stay unattributed, as they do anywhere else Clocktopus can't tell which project owns the work. A fork and its upstream aren't affected, since usually only the upstream is attached.
Fixes & improvements
- An email address that's already another account's main address can no longer be added as a second address on your account, whatever its capitalisation. One address answering to two accounts misfiled hours.
- "Merged" on the hours chart and on the delivery rail counted different things. Their labels now say which: merged that day, or opened in the period and merged since.