-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Clean and homogenize src/*/.gitignore
#1969
base: 2.x
Are you sure you want to change the base?
Conversation
68d6fdb
to
7934d3d
Compare
src/*/.gitattributes
src/*/.gitignore
d5be769
to
cce66e7
Compare
cce66e7
to
31df4f5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we double-check the .gitattributes in the same pass ?
To me, i think this should be something like .gitignore
.gitattributes
(without the assets line when/if not needed) Probably also add when necessary
Be careful Turbo has some custom CI ;) |
So is there still something to agree on here? Can i help you on something @Kocal ? |
I didn't take a look since, maybe tonight! |
I don't like adding generated files (phpunit/phpcs/.. cache) ... but if we use CI actions that commit (auto-CS ?) this makes sense. But i also realised all of those are already ignored in the root .gitignore .doctor-rst.cache
.php-cs-fixer.cache
node_modules
yarn-error.log
/composer.lock
/vendor (we may add phpunit.result.cache here) So, after your explanations, the package folders could contain: .gitignore# not sure if here .. maybe in the global gitignore
/.php-cs-fixer.cache
/.phpunit.result.cache
# is the root one not enough ?
/assets/node_modules/
/vendor/
/composer.lock
/phpunit.xml (with aditional files depending on the package content) .gitattributes/.gitattributes export-ignore
/.gitignore export-ignore
/.symfony.bundle.yaml export-ignore
/assets/src export-ignore
/assets/test export-ignore
/phpunit.xml.dist export-ignore
/tests export-ignore (with aditional files depending on the package content)
Side question @Kocal : So we may only need to update the root .gitignore one for now :) |
Not complicated, but really not wanted. With this kind of project structure you want to use Yarn workspaces (added in #9 :D) |
Rebased / clean in ##2243 .. LGTM ! |
Following @smnandre 's comment (#1937 (comment)), it looks like
src/*/.gitignore
files reference files that does not exist in the context of a Package.For example, ignoring
.php_cs.cache
from a package does not make sense, since this file is created by PHP-CS-Fixer at the repository root.Now, all the
src/*/.gitignore
contain at least this list: