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
Check out a branch that's synced, git commit --amend to change the hash of the last commit.
From the Source control: Git sidebar, select ... -> "push to...", then origin
The push will fail - as it should because your history doesn't match so you'd need to force push, but you don't get any error message to inform you that it failed.
If you instead use the ... -> Push option, then you get an error suggesting to git pull before pushing. I assume that this same error should be used for push to... as well.
VS Code version: Code 1.24.1 (24f6262, 2018-06-13T17:41:50.128Z)
OS version: Darwin x64 17.6.0
System Info
Item
Value
CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.
Issue Type: Bug
git commit --amend
to change the hash of the last commit.The push will fail - as it should because your history doesn't match so you'd need to force push, but you don't get any error message to inform you that it failed.
If you instead use the ... -> Push option, then you get an error suggesting to git pull before pushing. I assume that this same error should be used for
push to...
as well.VS Code version: Code 1.24.1 (24f6262, 2018-06-13T17:41:50.128Z)
OS version: Darwin x64 17.6.0
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
video_decode: enabled
video_encode: enabled
vpx_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (4)
The text was updated successfully, but these errors were encountered: