ios - Should we commit pod files to version control system (GIT or SVN)

Question

So far I was working on an app and my Team Lead said not to commit the pod files and I just followed his instructions.

Then our Lead changed and he said to commit the pod file to Git. So I was confused which one to go with.

Should we commit the pod file or not and if we should not then why. Please help me clear on this thing as I went through some articles as well but didn't find any satisfactory answer.

question from:https://stackoverflow.com/questions/45587084/should-we-commit-pod-files-to-version-control-system-git-or-svn

Answer 1

Whether or not you check in your Pods folder is up to you, as workflows vary from project to project. It is recommended that you keep the Pods directory under source control.

Benefits of checking in the Pods directory

1. After cloning the repo, the project can immediately build and run, even without having CocoaPods installed on the machine. There is no need to run pod install, and no Internet connection is necessary.
   
2. The Pod artifacts (code/libraries) are always available, even if the source of a Pod (e.g. GitHub) were to go down.
   
3. The Pod artifacts are guaranteed to be identical to those in the original installation after cloning the repo.
   

Benefits of ignoring the Pods directory

1. The source control repo will be smaller and take up less space.
2. As long as the sources (e.g. GitHub) for all Pods are available, CocoaPods is generally able to recreate the same installation. (Technically there is no guarantee that running pod install will fetch and recreate identical artifacts when not using a commit SHA in the Podfile. This is especially true when using zip files in the Podfile.)
3. There won't be any conflicts to deal with when performing source control operations, such as merging branches with different Pod versions.

Source: Cocoapods