Runs triggered against specific commit sha show in the UI whether the sha is in the tracked branch

Currently, when a run is triggered from a specific sha, the Spacelift UI does not show the branch, falling back instead to - . I asked this in the past in a Github issue and this is due to the difficulties of finding out the branch, as a commit can be in many branches.

However, what Spacelift knows, is whether the commit sha is in the tracked branch (and that is exposed to the policies via commit_exist_on_tracked_branch .

I would like that the UI of a commit sha triggered run in Spacelift does one of the following things:

  1. Either if commit_exist_on_tracked_branch is true, show the tracked branch name instead of -

  2. Or in the same line that the branch, sha, triggerer, etc information is shown, it show that the run is in a commit that belong to the tracked branch

I would favour 1, but 2 would be aceptable.

Workaround
The workaround is very hacky, the automation that triggers the run adds a comment in the run specifying the branch to which the commit belongs to.
Problem
When several PRs land at the same time in the tracked branch, runs against the head of the tracked branch (the ones that do show the branch info in the UI) can be triggered againts commits that are not the actual commit causing the run, making the run confusing, as the commit message is unrelated with what is actually happening in the run. It is more nuanced than this, but this is the short summary. I can give more details to support if needed.

Please authenticate to join the conversation.

Upvoters
Status

πŸ‘€ In Review

Board

πŸ’‘ Feature Requests

Tags

UI/UX

Date

About 5 hours ago

Subscribe to post

Get notified by email when there are changes.