Proposed commits loading async in the UI is confusing #657
Description
When I push a manifest commit to the DRY branch, the corresponding "proposed" commits appear in random order, sometimes several seconds apart. As a user, my mental model around commits is "I push one, and the promoter immediately starts deploying it through the environments." Seeing the commits arrive in random order undermines my confidence in the system. The async processes are implementation details that shouldn't be exposed to the user.
Instead of showing up async, the proposed commit should only be displayed once all environments are ready.
The UI should show some kind of "loading" or "waiting" indicator when the first proposed commit is available so that the user knows the others are coming.