Skip to content

feat(pull): show whether anything was pulled - #174

Merged
narnaud merged 1 commit into
narnaud:mainfrom
dfaure-kdab:wip/dfaure/pull-output
Jul 14, 2026
Merged

feat(pull): show whether anything was pulled#174
narnaud merged 1 commit into
narnaud:mainfrom
dfaure-kdab:wip/dfaure/pull-output

Conversation

@dfaure-kdab

Copy link
Copy Markdown
Collaborator

Before:
✓ Fetched latest changes
✓ Rebased onto upstream
✓ Updated submodules
✓ Updated branch wip-stack with origin/master (f7264ed Enforce commit message requirements)

After:
Total 35 (delta 16), reused 30 (delta 16)
From ssh://codereview.kdab.com:29418/kdab/KDABViewer
389626f55..f7264ed16 master -> origin/master
✓ Fetched latest changes
✓ Rebased onto upstream
✓ Updated submodules
✓ Updated branch wip-stack with origin/master (f7264ed Enforce commit message requirements)

(plus any new or deleted branches)

I need to know that new changes / branches have been pulled.
(to know if I need to rebuild; to look at what the cat brought in; etc.)

@dfaure-kdab
dfaure-kdab requested a review from narnaud as a code owner July 7, 2026 11:02

@narnaud narnaud left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to test this change.
The idea of the spinner was to show the user something is happening beyond the hood, without showing all the details. It was particularly important for the git sub-module, many times I thought I had a problem while it was taking some time to download changes with git (and it didn't show anything).
If you pass --no-progress, then we may have the same issue with the first step, no?
I wonder if we could have the spinner showing, and display the output of git just after, once done.

(again, I need to test the change to be sure)

Before:
✓ Fetched latest changes
✓ Rebased onto upstream
✓ Updated submodules
✓ Updated branch wip-stack with origin/master (f7264ed Enforce commit message requirements)

After:
Total 35 (delta 16), reused 30 (delta 16)
From ssh://codereview.kdab.com:29418/kdab/KDABViewer
   389626f55..f7264ed16  master     -> origin/master
✓ Fetched latest changes
✓ Rebased onto upstream
✓ Updated submodules
✓ Updated branch wip-stack with origin/master (f7264ed Enforce commit message requirements)

(plus any new or deleted branches)

I need to know that new changes / branches have been pulled.
(to know if I need to rebuild; to look at what the cat brought in; etc.)
@dfaure-kdab
dfaure-kdab force-pushed the wip/dfaure/pull-output branch from aa0cdde to 0af17b4 Compare July 8, 2026 11:21
@dfaure-kdab

Copy link
Copy Markdown
Collaborator Author

OK now with the spinner kept, and the output afterwards.

@dfaure-kdab

Copy link
Copy Markdown
Collaborator Author

Tested with a very big submodule update, worked nicely.

@narnaud
narnaud merged commit 1bc9ed1 into narnaud:main Jul 14, 2026
4 checks passed
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.

2 participants