Amplify-cli: What Amplify files should be .gitignored for projects that are shared across developer machines?

[jkeys-ecg-nmsu]

It seems like, at the very least, local-env-info.json should be .gitignored, because whoever last pushed to the master branch will break the local environment of whoever next pulls from master.

What other files should be .gitignored to minimize Amplify conflicts when developers are sharing the same backend?

* Provide additional details e.g. code snippets *
We've been stepping on each other's toes a lot, breaking environments, manually editing local-env-info.json (*this breaks on Windows btw, it does not correctly generate paths that go into the /mnt/c/* directory *), getting merge conflicts because of last push timestamps, etc.

[kaustavghosh06]

@jkeys-ecg-nmsu When you initialize a project using the latest version of the CLI, we create or append to your existing .gitignore file. We recommend ignoring the following files/folders.

amplify/\#current-cloud-backend
amplify/.config/local-*
amplify/backend/amplify-meta.json
amplify/backend/awscloudformation
build/
dist/
node_modules/
aws-exports.js
awsconfiguration.json

[jkeys-ecg-nmsu]

Ah, and indeed these are a part of our .gitignore. So many pointless merges :P So it's a git cache issue then. Problem solved!

To anyone who finds themselves in a similar situation, this is the remedy:

git rm -rf --cached .
git add .

Thanks!

[arelaxend]

@kaustavghosh06
It looks unsecured to commit team-provider-info.json in git repository while it may contains provider credentials.