Allow for custom build id/name

[GrumpyMeow]

Feature request

I see that for build id a number is being used. It would be nice-to-have to allow for overriding the build-id name in Chromatic Web UI.
This to allow for aligning our the version-name of our CI-build with Chromatic. This would make tracing visual changes back to our builds easier.
We are using Azure DevOps.

Proposed solution

Allow for setting an environment variable which should be used as the build id (prefix) in Chromatic.

[hvgeertruy]

We would really like this as well.

That way it is clear for the consumers of the storybook which version of the component library they are looking at

Alternatively, we tried an implementation where we pointed the branch to a specific version tag, so the branch value would be the version number, but this is not ideal because that would mean that the url would change for every build (which would make bookmarks or references to Design systems (like frontify/zero-height) pretty useless.

The ability to override the build number/pass the version number from the package.json would be much more useful than YABN (yet another build number :)

[michelbarakat]

This would be highly appreciated.
A build name override will help track the releases properly

[meeshh]

Any news on this requested feature?
It would be really nice to have in order to tie our generated versions to the published build