After committing locally, a city developer needs the shared team repository to receive those commits so colleagues can pull the latest work. Which source-control action accomplishes that?
Select an answer to reveal the explanation.
Short Explanation
Commit is local; push is ‘send it to the shared fridge.’ Until you push, the rest of the city team still sees yesterday’s leftovers. Remotes exist so nobody’s laptop is the single source of truth.
Full Explanation
A push transfers local commits to a remote repository so collaborators and automation can access the updated history. Municipal teams depend on remotes for shared visibility and CI triggers. Rebase, squash, or tagging operations do not by themselves publish commit history to the shared remote in place of a push.