Separate development and deployment git repositories

Question

I recently came across an approach of managing a project and its deliverable. Project team was using git repository for development. There was another repository being used

Answer 1

The main benefit is to keep deliverable artifacts (which can be large and can include binaries) separate from the source repo.

• the main repo remains a source-only repo (meaning text content, no -- or few and small -- binaries)
• the delivery repo:
  • is managed independently,
  • doesn't have to be cloned completely (a shallow clone can be enough, since that feature has been improved recently)
  • can be "cleanup" if necessary (trimming old deliveries now obsolete)

The main inconvenient (for both approaches) is to keep binaries in a git repo (which isn't a good fit for such artifacts).
Alternatives exist (using git): git-annex, bup, ....
Or you can store those deliverable in a dedicated referential, like Nexus (which is different from a git repo)