git - Why are there unstaged files after a synchronization?

Question

For reference check this answer to see what is repo.

There is a situation that I cannot understand and I would like someone to explain to me.

So far I have been using repo sync to synchronize my code with a series of repositories. After I did this and I did repo status I could see a clean state. (repo status is like git status for all repositories)

However lately when I do that, I got a series of "modified" files. It is like doing git status and getting a lot of "changes not staged for commit" (modified: afile.ext)

Why is this happening? I thought once you synchronize you get the state of your repositories with the latest changes.

My git knowledge is failing me here. Any thoughts?

question from:https://stackoverflow.com/questions/65910906/why-are-there-unstaged-files-after-a-synchronization

Answer 1

According to the docs, repo sync is the equivalent of git fetch followed by a rebase. So it brings your remote-tracking branches into sync with the actual remote branches, and causes your current branch to be rebased onto the end of the remote tracking branch, but it has no effect on your working tree or the index or wherever the "modified" files are. You would still presumably need to say what you want done with the "modified" files: add-and-commit them, for instance.