GIT: How to see pulled/pushed changes in origin

by

It looks like the question Why won’t I see changes in the remote repo after “git push”?

The push operation is always about propagating the repository history and updating the refs, and never touches the working tree files.
In particular, if you push to update the branch that is checked out in a remote repository the files in the work tree will not be updated.

This is a precautionary design decision.
The remote repository’s work tree may have local changes, and there is no way for you, who are pushing into the remote repository, to resolve conflicts between the changes you are pushing and the ones in the work tree

As said, a bare remote repo is better here.
You can setup a non-bare repo in the same place than MAIN CODEBASE, in order to see the changes in that “non-bare main codebase repo”.

Note: with the upcoming Git 1.7, git push into a branch that is currently checked out (i.e. pointed by HEAD in a repository that is not bare) will be refused by default.

git pull should not overwrite anything, at least not without big warnings. Do you see any of those warning messages?

As kibitzer aptly describes in the comment:

bare means a repository which does not contain the actual files, just the metadata (commits). Pushes to such repository are safe because no discrepancy is generated between the state of files on disk and commits in .git

The fact that this remote repo is “empty” (it only has the .git folder, but no file checked-out) does not mean a git clone will result in an empty local repo.
It will create and check-out an initial branch that is forked from the cloned repository’s currently active branch.

So, the “publication architecture” would be:

/---
| MAIN SERVER   :   [     BARE-MAIN-REPO    ] == (pull only) ==> [ MAIN-REPO ]
\---                    ^^    ||   ^^   ||
                        ||    ||   ||   ||
                       push  pull push pull
                        ||    ||   ||   ||
/---                    ||    vv   ||   ||
|DEV1 PC        :    [ DEV1 REPO ] ||   ||
\---                               ||   ||
                                   ||   ||
/---                               ||   vv
|DEV2 PC        :               [ DEV2 REPO ]
\---

Note: if you refer to the Git Glossary, what “origin” means is the default upstream repository.
Bare-main-Repo is the “origin”, i.e. the default upstream repo for dev1 and dev2, meaning both those repos wll have been created by cloning Bare-main-Repo.
(Nothing prevents you to add other upstream repos: dev1 could add dev2 as another upstream repo, allowing to pull directly from dev2 for instance)

More Related Contents:

  1. Definition of “downstream” and “upstream”
  2. How to find the nearest parent of a Git branch
  3. How do I view ‘git diff’ output with my preferred diff tool/ viewer?
  4. How to find/identify large commits in git history?
  5. SSL certificate rejected trying to access GitHub over HTTPS behind firewall
  6. Git 1.6.4 beta on Windows (msysgit) – Unix or DOS line termination
  7. Combining multiple commits before pushing in Git [duplicate]
  8. Whitelisting and subdirectories in Git
  9. git push to multiple repositories simultaneously [duplicate]
  10. How do I revert a merge commit that has already been pushed to remote?
  11. How do I remove local (untracked) files from the current Git working tree?
  12. Why does Git tell me “Not currently on any branch” after I run “git checkout origin/”?
  13. How do I make git block commits if user email isn’t set?
  14. Difference between git stash pop and git stash apply
  15. Merging between forks in GitHub
  16. Git – finding a filename from a SHA1
  17. Gerrit error when Change-Id in commit messages are missing
  18. Is it possible to have different Git configuration for different projects?
  19. git remote add with other SSH port
  20. git status shows fatal: bad object HEAD
  21. Export a stash to another computer
  22. How to undo a git pull?
  23. Git submodules not updating in Jenkins build
  24. fatal: The upstream branch of your current branch does not match the name of your current branch
  25. Egit hooks do not get triggered
  26. How to use git sparse-checkout in 2.27+
  27. “Cannot update paths and switch to branch at the same time”
  28. How to reduce git repo size on Bitbucket?
  29. How to convert a Git repo to a submodule, which is nested in another (parent) Git repo?
  30. ‘git log’ output encoding issues in Windows 10 CLI terminal

Leave a Comment