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

Configuration files #11

Merged

Conversation

andresmoschini
Copy link
Member

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.

.yardoc
_yardoc


Copy link
Contributor

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?

Copy link
Member Author

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.

Copy link
Member

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.

Copy link
Member Author

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.

Copy link
Member

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).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

·#15 created for this.

@matiasbeckerle
Copy link
Contributor

I think this is one of the best pull requests of the documentation. A very useful information here. Thanks, good job!

@andresmoschini
Copy link
Member Author

Thanks Matias, I am merging in order to add a new one, hehe

andresmoschini added a commit that referenced this pull request Mar 7, 2014
@andresmoschini andresmoschini merged commit 8ccd51f into MakingSense:gh-pages Mar 7, 2014
@andresmoschini andresmoschini deleted the configuration-files branch March 7, 2014 20:07
*.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).
Copy link
Member

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?

Copy link
Member Author

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Agreed.

@AlphaGit
Copy link
Member

Aside from those two comments of mine, everything else looks great to me!

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

Successfully merging this pull request may close these issues.

3 participants