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
When I trigger a deploy from my machine, I might forget sometimes to pull. Thus I package happily from what I thought to be HEAD. I also tried to fetch, but even when I see that FETCH_HEAD is different than HEAD, the build still succeeds.
Could I have some kind of validation which would fail if the checked out branch is not synced with its origin? I'd like to see it failing the build the same why like the validation for uncommited changes.
I'm aware this wouldn't be an issue if the CI would work but well..
The text was updated successfully, but these errors were encountered:
When I trigger a deploy from my machine, I might forget sometimes to pull. Thus I package happily from what I thought to be HEAD. I also tried to fetch, but even when I see that FETCH_HEAD is different than HEAD, the build still succeeds.
Could I have some kind of validation which would fail if the checked out branch is not synced with its origin? I'd like to see it failing the build the same why like the validation for uncommited changes.
I'm aware this wouldn't be an issue if the CI would work but well..
The text was updated successfully, but these errors were encountered: