Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yarn.lock is beign ignored #22072

Closed
snitin315 opened this issue Mar 8, 2020 · 2 comments · Fixed by #22196
Closed

yarn.lock is beign ignored #22072

snitin315 opened this issue Mar 8, 2020 · 2 comments · Fixed by #22196
Labels
type: bug An issue or pull request relating to a bug in Gatsby

Comments

@snitin315
Copy link
Contributor

Description

yarn.lock file is being ignored inside .gitignore , but I can see that the repository do have yarn.lock file.

Describe the issue that you're seeing.

Expected result

yarn.lock should not be inside .gitignore

What should happen?

remove yarn.lock from .gitignore

Actual result

What happened.

Environment

Run gatsby info --clipboard in your project directory and paste the output here.

@snitin315 snitin315 added the type: bug An issue or pull request relating to a bug in Gatsby label Mar 8, 2020
@nayres
Copy link
Contributor

nayres commented Mar 8, 2020

Have you pushed yarn.lock to be tracked by git prior to ignoring it? If so, git is still tracking the file. You can run:

git rm --cached .
git add .
git commit -m "Remove ignored files from git"

This will update git and your file will no longer be tracked.

@snitin315
Copy link
Contributor Author

snitin315 commented Mar 12, 2020

What I want to say that the project has yarn.lock file, but we are also ignoring it .

Screenshot from 2020-03-12 06-51-37

corresponding .gitignore -

Screenshot from 2020-03-12 06-51-55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants