Skip to content

Conversation

@drothlis
Copy link
Contributor

@drothlis drothlis commented May 20, 2025

Otherwise pressing the sync button when there are upstream changes (e.g. commits created on the Stb-tester Portal, such as new AI training screenshots or new Page Objects) fails, with this in the logs:

You have divergent branches and need to specify how to reconcile them.
You can do so by running one of the following commands sometime before
your next pull:

git config pull.rebase false  # merge (the default strategy)
git config pull.rebase true   # rebase
git config pull.ff only       # fast-forward only

@drothlis
Copy link
Contributor Author

I want to dog-food this setting for a while before I merge this.

Otherwise pressing the sync button when there are upstream changes (e.g.
commits created on the Stb-tester Portal, such as new AI training
screenshots or new Page Objects) fails, with this in the logs:

> You have divergent branches and need to specify how to reconcile them.
> You can do so by running one of the following commands sometime before
> your next pull:
>
>   git config pull.rebase false  # merge (the default strategy)
>   git config pull.rebase true   # rebase
>   git config pull.ff only       # fast-forward only
@wmanley
Copy link
Contributor

wmanley commented Oct 24, 2025

This came up again recently in a trial. I think it's the right thing to do, at least if it doesn't override existing preference.

@drothlis drothlis merged commit fe6b131 into main Oct 28, 2025
8 of 13 checks passed
@drothlis drothlis deleted the vscode-rebase branch October 28, 2025 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants