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
This may be 'expected' but I found it surprising. I don't like the default 'merge' of --checkout, so I use ---rebase so as not to arbitrarily change the history with merge commits.
I issued this command to update to release 92: git ensembl --checkout --branch release/92 --secondary_branch master --rebase available
However, when I then cd to ensembl and hit 'git status', I see: Your branch is behind 'origin/release/92' by 4 commits, and can be fast-forwarded.
i.e. Although it got the latest commits, it didn't --rebase
Skipping checkout as we are already on release/92
Should I use --pull instead?
The text was updated successfully, but these errors were encountered:
This may be 'expected' but I found it surprising. I don't like the default 'merge' of --checkout, so I use ---rebase so as not to arbitrarily change the history with merge commits.
I issued this command to update to release 92:
git ensembl --checkout --branch release/92 --secondary_branch master --rebase available
However, when I then cd to ensembl and hit 'git status', I see:
Your branch is behind 'origin/release/92' by 4 commits, and can be fast-forwarded.
i.e. Although it got the latest commits, it didn't --rebase
Should I use --pull instead?
The text was updated successfully, but these errors were encountered: