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

Use .gitkeep instead of multiple empty .gitignores #13

Open
MahdiBaghbani opened this issue Nov 18, 2022 · 4 comments
Open

Use .gitkeep instead of multiple empty .gitignores #13

MahdiBaghbani opened this issue Nov 18, 2022 · 4 comments
Assignees

Comments

@MahdiBaghbani
Copy link
Member

discussed in #12

@MahdiBaghbani MahdiBaghbani changed the title Use .gitkeep instead of git ignore Use .gitkeep instead of multiple empty .gitignore s Nov 18, 2022
@MahdiBaghbani MahdiBaghbani changed the title Use .gitkeep instead of multiple empty .gitignore s Use .gitkeep instead of multiple empty .gitignores Nov 18, 2022
@michielbdejong
Copy link
Member

I just read about it as well, it's explained well in https://stackoverflow.com/questions/7229885/what-are-the-differences-between-gitignore-and-gitkeep

@MahdiBaghbani
Copy link
Member Author

MahdiBaghbani commented Nov 18, 2022

I think that we really don't want those files at all, /bootstrap and /storage inner directories such as cache and sessions are created during Laravel app runtime, for caching and other stuff.
I was kinda wrong to add empty .gitignores, should we add storage and bootstrap to our main .gitignore in the root of project?

@michielbdejong
Copy link
Member

@michielbdejong
Copy link
Member

Good point, that's probably how Laravel development on git is supposed to work.

@MahdiBaghbani MahdiBaghbani self-assigned this Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants