When a user manually runs different custom builds against a branch (same commit), for example, custom1 and custom2 runs against commit abc, only the latest run is shown in the commit build status, since the same type of pipeline was run on the same commit (or even in the pull request build status if the commit branch is the source branch of that pull request). As long as the build status key, commit, or ref name is different, we show all the builds on the commit. In this case, the build key was the same, which was why we are not showing the two builds from 2 different custom steps run on the same commit, ref.

This can be confusing since each custom build run may have a different purpose or goal, even though they run on the same commit. Ideally, all the custom builds of their latest run should be shown in the commit build status tagged with different build keys, rather than only showing the latest of all custom builds together.