Skip to content

Commit d51e7cf

Browse files
Copilotalexr00
andcommitted
Only pull after GraphQL update, not after REST API conflict resolution
Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
1 parent 19856a3 commit d51e7cf

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

src/github/folderRepositoryManager.ts

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2473,8 +2473,9 @@ export class FolderRepositoryManager extends Disposable {
24732473

24742474
if (continueWithMerge) {
24752475
const updateSucceeded = await pullRequest.updateBranch(conflictModel);
2476-
// If the PR is currently checked out and update succeeded, pull to sync local branch
2477-
if (updateSucceeded && pullRequest.isActive && !isBrowser) {
2476+
// If the PR is currently checked out and update succeeded via GraphQL (no conflicts), pull to sync local branch
2477+
// When there are conflicts (REST API path), the update already pushes the changes, so no pull is needed
2478+
if (updateSucceeded && pullRequest.isActive && !isBrowser && hasNoConflicts) {
24782479
await this.repository.pull();
24792480
}
24802481
return updateSucceeded;

0 commit comments

Comments
 (0)