Sally and Nicole are working in the same codebase. They will be changing different files of the same repositories because of their requirement change. They both want to keep their code separated while...

Extracted text: Sally and Nicole are working in the same codebase. They will be changing different files of the same repositories because of their requirement change. They both want to keep their code separated while they are working in the same repositories before pushing to the production or single codebase 'master branch'. Which of the following technique might help in maintaining the two different versions of their code using Git so that they could finally merge the final code to the same master branch? O a. Create their own branch and push the code to the respective branch prior to pushing to the master branch O b. Ask whose code is important first, and let them work first O c. Create their own repositories and try to merge the code. Given there might be similar features and differ the implementation of the code. O d. None of the given idea will work