-
Notifications
You must be signed in to change notification settings - Fork 14
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
Configuration files #11
Configuration files #11
Conversation
.yardoc | ||
_yardoc | ||
|
||
|
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 example would be an universal-and-for-all-the-projects or what? What if I want to put my example .gitignore for an Android app?
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.
Mmmm, my idea is to have an universal recommendation. If you have an specific .gitignore file for android I suggest you to include all non-problematic lines in current file. And also you could add a clean link for your .gitignore file for android.
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.
I disagree with the "global" recommendation strategy. Different technologies will generate different "crap" that we want to ignore automatically, and we will want developers to be aware of what they add and what they exclude, making a conscious decision.
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.
I agree with you, but I also want to provide an easy way to start a project. I think that it is better to start a new project with this .gitignore
file than start without any .gitignore
. Also you can adapt it as you want, or use it to take some lines for a new one.
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.
Agreed. I'll add an issue to the repo so that we can discuss, and if most of us agree, we'll close the ticket when somebody implements the solution (whatever the solution is).
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.
·#15 created for this.
I think this is one of the best pull requests of the documentation. A very useful information here. Thanks, good job! |
Thanks Matias, I am merging in order to add a new one, hehe |
*.css -text | ||
*.less -text | ||
|
||
You can see a `.gitattributes` file example [in our GitHub repository](https://github.com/MakingSense/migration-to-git/tree/gh-pages/3-working-with-git/examples/.gitattributes). |
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.
Could we use relative links in here so that this works in forks too?
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.
No, because I want to link the file in GitHub and not in GitHub Pages, what do yuo think?
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.
Good point. Agreed.
Aside from those two comments of mine, everything else looks great to me! |
HI @matiasbeckerle, @noeliasfranco, @AlphaGit
I have added examples of
.gitignore
and.gitattributes
files, a description of them, a description of.gitconfig
and also an article about dealing with line endings.