-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
added .gitattributes file #130
added .gitattributes file #130
Conversation
@@ -0,0 +1,4 @@ | |||
.editorconfig export-ignore |
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.
Why not .*
?
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.
we can...
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.
done
Could we add the documentation part? |
.gitignore export-ignore | ||
CONTRIBUTING.md export-ignore | ||
|
||
/Resources/doc export-ignore |
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.
This is not always this path. Pleas use {{ docs_path }}
instead.
Example:
Line 17 in ae18f3e
cd {{ docs_path }} && sphinx-build -W -b html -d _build/doctrees . _build/html |
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.
done
What about tests? |
I would like #116 consensus before work on this. |
i got this error:
|
Maybe name it |
sound good, what do you think @soullivaneuh ? |
@OskarStark Yes you can. In this case, the Twig variable name would be |
so |
@OskarStark Well, it's a Twig file! So AFAIK you still need to use |
Exactly thats why i was asking! so now we should be fine! 👍
I was wondering, because this was already done at this point ;-) |
@@ -0,0 +1,4 @@ | |||
.* export-ignore | |||
CONTRIBUTING.md export-ignore |
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.
*.md
? Except if somebody want to keep a specific .md
file...
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.
*.md? Except if somebody want to keep a specific .md file...
i like the idea 👍
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.
done
i removed the indention, because we don't know the length of the docs path.... |
Hmm... or we can just specify the two cases ( I don't think git will cry if a ignored path does not exist, will do? |
no it won't but the indention is anyway bad if we add something like |
What's wrong with the Twig variable? |
Maybe, but I never seen a |
https://git-scm.com/book/uz/v2/Customizing-Git-Git-Attributes#Merge-Strategies |
|
Nothing i thought i should change |
No I meant why not use it, but I get it know, it was all about alignment |
for example when we use this:
this would be the result:
you know what i mean? |
Yes. Headaches ahead if we do that, as you explained. |
@OskarStark Looks good. Can you try it on a one of your forked sonata project? After that, I would like @rande opinion for this before merge because I got a refusal from him last time and he broke my heart. 💔 😛 |
@soullivaneuh You should also ask the community ;) |
Indeed, we might start a pool. I'll look for this week-end or next week. 👍 |
done @soullivaneuh |
Thanks @OskarStark, this will be merged soon. If you want to, you could open an issue to discuss about documentation ignore with vote. |
i agree with @rande that documentation could be helpful in some rare cases, so for me this is fine as a first step! |
Maybe we should remove |
sounds reasonable... @greg0ire @soullivaneuh what do you think? |
@@ -0,0 +1,2 @@ | |||
.* export-ignore | |||
*.md export-ignore |
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.
When removing all Upgrade*.md
and Readme.md
files, we should also remove the docs.
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.
When removing all
Upgrade*.md
andReadme.md
files, we should also remove the docs.Quite agree but let's discuss about this on another PR/issue! 👍
Then we should remove this entry.
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.
@rande Talk about keeping the docs folder, not the md files. Plus, the README.md
file is just a generic one with a link pointing to the online documentation.
So let's keep as is for now and launch a vote for docs folders.
I agree! |
Agree.
Quite agree but let's discuss about this on another PR/issue! 👍 |
but, if we remove the |
We don't care on this case, it's applies only for tarballs, not clones. |
We don't need the phpunit config outside the bundle, but some bundles depends on the |
Yeah, but this should be removed, shouldn't be? |
Yes, but we can't remove them in all minor versions. |
Already discussed on the concerned issue: This have to be fixed internally on minor versions. We don't care about external usage because it should not be used at all. |
We can now remove the |
Ping @OskarStark |
done @core23 |
I did everything, can you please merge this @soullivaneuh ? |
Can we please merge this @soullivaneuh ? |
ping @soullivaneuh |
Can we merge this @soullivaneuh ? |
Ping @soullivaneuh |
Closes #129