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
Currently loading backups will directly load whatever is on the remote backup branch. However, this is not safe to do when the remote backup branch is ahead of your actual branch.
For example, say I created a backup branch gbs-backup-example for my branch example. If my local example branch is at commit X. and my remote/gbs-backup-example is at commit X+2, we shouldn't directly bring in the work in progress from the remote.
Instead, after we detect such a scenario, we should create a stern warning for the user with a popup window, ask if they are certain, and only proceed when they confirm.
The text was updated successfully, but these errors were encountered:
Currently loading backups will directly load whatever is on the remote backup branch. However, this is not safe to do when the remote backup branch is ahead of your actual branch.
For example, say I created a backup branch
gbs-backup-example
for my branchexample
. If my localexample
branch is at commit X. and myremote/gbs-backup-example
is at commit X+2, we shouldn't directly bring in the work in progress from the remote.Instead, after we detect such a scenario, we should create a stern warning for the user with a popup window, ask if they are certain, and only proceed when they confirm.
The text was updated successfully, but these errors were encountered: