What supports offline use in Git development?

The local copy of project history is critical for supporting offline use in Git development because it allows developers to have the entire repository, including its history, stored on their local machines. This means that when a developer is disconnected from the internet, they can still create new branches, make commits, and view previous versions of the project without relying on a central server.

In contrast, centralized version control relies on a single server containing the repository and requires constant connectivity to perform operations. Dependency management, while important in many development environments, does not directly relate to offline capabilities. Similarly, exclusive online operations clearly point to a setup that would disrupt any possibility of offline work, making it counterproductive for developers who may need to work without an internet connection. Thus, having a local copy of the project history is what empowers developers using Git to function independently of network constraints.