Open amitsaha opened 5 years ago
Ok, so it looks like the Author that you provide must be a valid user in the organization, otherwise we fall back to the token owner.
Ah right, thanks. But isn't that logic a bit awkward? The commit author doesn't necessarily have to be the one who pushed the commit and hence created the build.
Alternatively, is there another field to communicate whose commit triggered the build?
Perhaps I didn't explain myself well, you can provide any author you like, provided they are a user in your Buildkite org. Is the author you are specifying not part of your org?
Right, i should have been a bit more descriptive. No, not all authors are members of the organization.
Hmmm 🤔So the author you are providing is in your org and it's still using the token creator? That's unexpected. Mind shooting me details in the support ticket of the build and I will look?
Ah. Misread what you wrote.
Nah, it makes sense. My custom client has been triggering builds by the same commit author who is not a member of the org. Given that scenario, is there any other way to show commit information for these commits without falling back to the token creator?
I am also having this issue - in the context where we make the API call to trigger a build, the reconciliation between username and actual org email/name is only best-effort (and some users aren't part of the buildkite org at all).
It would be great if we were allowed to use arbitrary author names instead of falling back to the token creator
Are there any updates on this?
I am using a custom client to create a build via the API. My payload looks as follows:
However, the UI still shows the API token creator as the build creator.
Any idea what I am doing wrong?