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

Do we need .gitattributes file? #129

Closed
OskarStark opened this issue Jun 1, 2016 · 17 comments
Closed

Do we need .gitattributes file? #129

OskarStark opened this issue Jun 1, 2016 · 17 comments

Comments

@OskarStark
Copy link
Member

Something like this:

.editorconfig    export-ignore
.gitattributes   export-ignore
.gitignore       export-ignore
CONTRIBUTING.md  export-ignore

Please use 👍 or 👎 to vote!

@greg0ire
Copy link
Contributor

greg0ire commented Jun 1, 2016

@soullivaneuh IIRC, you told me this is specific to github… is there a way to get the same effect from a file in the .github directory ?

@OskarStark
Copy link
Member Author

i will create a PR with this file as a first draft

@OskarStark OskarStark self-assigned this Jun 1, 2016
@soullivaneuh
Copy link
Member

soullivaneuh commented Jun 1, 2016

Personally 👍 and the doc path could be removed too as the documentation should be compiled and online,

But I already proposed something like that a year, and @rande declined the proposition: sonata-project/SonataAdminBundle#3043 (comment)

But I noticed an interesting comment of him:

I think it is not the top priority as this need to be done on all sonata repositories ;)

With dev-kit we can do this now.

So @rande, what it your opinion for this? :-)

@greg0ire
Copy link
Contributor

greg0ire commented Jun 1, 2016

IIRC, you told me this is specific to github

Looks like it is not : http://stackoverflow.com/questions/21832151/git-archive-export-ignore-ignoring-directories

@soullivaneuh
Copy link
Member

@soullivaneuh IIRC, you told me this is specific to github… is there a way to get the same effect from a file in the .github directory ?

I think the export-ignore rule is specific to GitHub, not the .gitattributes file.

@soullivaneuh soullivaneuh changed the title Do we need .gitattributes files? Do we need .gitattributes file? Jun 1, 2016
@greg0ire
Copy link
Contributor

greg0ire commented Jun 1, 2016

I think the export-ignore rule is specific to GitHub, not the .gitattributes file.

Have you seen my link above ? Or is GH lagging again ? I think it is specific to git archive

Also this will not save a lot of space, archives are zipped. So closing the issue is a good option

inodes matter too, and when searching for a file, not having tests show up would help. It will make fzf even faster so 👍

@soullivaneuh
Copy link
Member

Have you seen my link above ? Or is GH lagging again ? I think it is specific to git archive

I saw it while writing my answer. Yes indeed. 👍

@greg0ire
Copy link
Contributor

greg0ire commented Jun 1, 2016

fzf

fzf or any other fuzzy-matcher, indexation tool. Give this one a try though, it also integrates with the shell to replace Ctrl+R

@rande
Copy link
Member

rande commented Jun 2, 2016

Actually, I learn a lot from codes (php, doc and test) when debugging projects inside vendor's folders. Removing, those files will not help people working offline (yes ...) or people jumping into the vendor's directory directly.

Also, this will not save that much space maybe a few KB over 50MB

@soullivaneuh
Copy link
Member

Actually, I learn a lot from codes (php, doc and test) when debugging projects inside vendor's folders. Removing, those files will not help people working offline (yes ...) or people jumping into the vendor's directory directly.

@rande If they want the complete folder on some case, they can use composer install --prefer-source.

No tarball downloaded, so no ignored file. Export ignore is just for tarballs.

What do you think?

@rande
Copy link
Member

rande commented Jun 2, 2016

Install with prefer-source can took up to 20 min, where prefer-dist is about a minute ... Also, not sure people are aware about this feature and might just think there is no documentation.

@rande
Copy link
Member

rande commented Jun 2, 2016

also you should sum the size of those folders to really make sure it is worth it...

@soullivaneuh
Copy link
Member

also you should sum the size of those folders to really make sure it is worth it...

Depends on projects I would say.

But there is also the @greg0ire argument: #129 (comment)

I quite agree with him. Sometime using a fuzzy search on my IDE, I can fall on a class that looks like a real class but no, it's a fixture. Pretty frustrating. But yeah, it's a personal opinion. 😉

@soullivaneuh
Copy link
Member

and might just think there is no documentation.

About that, documentation is on rst format. This format is not nice to read.

Alternatively, we can exclude the README.md from export-ignore that provide a link to online documentation, or simply add a special file for it?

@rande
Copy link
Member

rande commented Jun 2, 2016

Tools' constraints is out of the scope here! BTW I have PHPStorem licence for Sonata's contributors ;)

@greg0ire
Copy link
Contributor

greg0ire commented Jun 3, 2016

also you should sum the size of those folders to really make sure it is worth it...

the number of files is a concern too (the number of inodes is finite)

@OskarStark
Copy link
Member Author

Tools' constraints is out of the scope here! BTW I have PHPStorem licence for Sonata's contributors ;)

sounds nice 👍 how can i get this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants