Question

Changesets originating by my build server are marked with the access token used for that. Despite the fact that this doesn't fit into the column width it is just hard to read. I suggest showing the description of the access token instead for better readability.

Answer 1

Just to clarify: the pusher does indeed show the description of the access token used. Are you looking at the committer?

We didn't intend for access tokens to be used as the committer name. Just the authentication name. The ui.username for a repository can be anything; here at Fog Creek, we set it to Mortar <thecisystem@fogcreek.com>. We then have it authenticate using an access token.

While substituting the description of an access token for the committer is a reasonable request, committing as an access token is a serious security vulnerability, since it gives anyone with access to your repository either global read or (worse) write permission. So this is almost assuredly not what you want to do.

That said, we'll add support for showing the description of an access token, rather than its GUID, in a later release of Kiln. Just understand that you still have serious security problems if you're using access tokens this way.