0

I'm working with a Firebase Cloud Functions project and it has two branches main for production and development for staging. Because production and staging are linked to different Firebase projects both branches need different config files (such as serviceAccountKey.json)

my question is:

Is possibile whenever I make a PR in Github to pick which changes need to be merged, and which to be discarded?

Because every time I merge, the production config files are overwritten by the staging ones.

I don't know if that's the proper way to manage those type of situations but in general I would like to know if such a feature is possible.

Thanks.

Matteo De Lucia
  • 1
  • 1
  • Does this answer your question? [Git best practice for config files etc](https://stackoverflow.com/questions/9342886/git-best-practice-for-config-files-etc) – Orace Oct 19 '21 at 15:39

1 Answers1

0

Just add the serviceAccountKey.json in the .gitignore file list and provide a serviceAccountKey-template.json for new comers.

Orace
  • 7,822
  • 30
  • 45