Add yarn.lock across the project to .gitignore

[elit-altum]

What is the context for this discussion?

While making any changes to the codebase yarn.lock in multiple sub-directories is changed while setting up the project. Which in turn will come up as a commit in a PR and pollute it.

Elaborate on the discussion topic.

Looking at the scenario I can suggest the following options:

1. Add all lock files to gitignore so they are not tracked by git in the future.
2. Enforce all future installations of the codebase to use the same lock file by suggesting devs to use yarn install --frozen-lockfile instead of yarn install for the future setups. [ reference ]

Stakeholders

I think all devs making their contribution for the first time will face this issue.

[Swapnil-2001]

@elit-altum can I make a PR adding lock files to gitignore?

[elit-altum]

@Swapnil-2001 I have opened this thread for discussion here, I already have a PR ready for this!

[Swapnil-2001]

Oh okay okay.

[jbuckner]

What is the issue that's happening here? Are you seeing the yarn.lock file change?