You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use a private Bitbucket Server at work, so we cannot use the Git integration and have to use the Vercel CLI to deploy instead. This works fine, but there's currently no way to tell what a deployment originated from, as all deployments just say "via Vercel CLI" and "Branch: No repository". Since #7910 was merged, the Git metadata is extracted and sent to the create deployment API, however it appears to simply discard it when the project is not connected to Git, as it doesn't end up in the dashboard.
I understand that you wouldn't be able to link to the appropriate commit or branch, but at least showing the branch name, commit message and hash would go a long way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We use a private Bitbucket Server at work, so we cannot use the Git integration and have to use the Vercel CLI to deploy instead. This works fine, but there's currently no way to tell what a deployment originated from, as all deployments just say "via Vercel CLI" and "Branch: No repository". Since #7910 was merged, the Git metadata is extracted and sent to the create deployment API, however it appears to simply discard it when the project is not connected to Git, as it doesn't end up in the dashboard.
I understand that you wouldn't be able to link to the appropriate commit or branch, but at least showing the branch name, commit message and hash would go a long way.
Beta Was this translation helpful? Give feedback.
All reactions