usage of "latest" badge is pretty confusing
The usage of the "latest" badge is based on the "latest" commit - and therefore pretty confusing when pinned on a pipeline since it suggests that it means "latest pipeline run". based on commits it can occur twice, as one can see in the documentation:
Steps to reproduce
run a pipeline twice based on a singe commit. a pipeline may fails or succeeds when there are changes in dependencies.
What is the expected correct behavior?
i would expect a «latest» badge on the latest pipeline only. may another badge pins on the latest commit id (so one can determine the last where a pipeline was triggered from later commits that skipped the pipeline.)