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

new: dev: Untrack typical files #15

Closed
wants to merge 1 commit into from

Conversation

beeftornado
Copy link
Contributor

No description provided.

@beeftornado beeftornado closed this Oct 3, 2014
@beeftornado beeftornado deleted the gitignore branch October 3, 2014 06:16
@vaab
Copy link
Owner

vaab commented Oct 3, 2014

For the logs: we choose to limit repository's .gitignore to local concerns. Any global patterns that should be avoided should be put in your global gitignore. Following the sane policies described in: http://git-scm.com/docs/gitignore

Here's the pertinent excerpt:

Which file to place a pattern in depends on how the pattern is meant to be used:

Patterns which should be version-controlled and distributed to other repositories via clone (i.e., files that all developers will want to ignore) should go into a .gitignore file.

Patterns which are specific to a particular repository but which do not need to be shared with other related repositories (e.g., auxiliary files that live inside the repository but are specific to one user’s workflow) should go into the $GIT_DIR/info/exclude file.

Patterns which a user wants Git to ignore in all situations (e.g., backup or temporary files generated by the user’s editor of choice) generally go into a file specified by core.excludesfile in the user’s ~/.gitconfig. Its default value is $XDG_CONFIG_HOME/git/ignore. If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore is used instead.

@vaab vaab mentioned this pull request Apr 28, 2015
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.

None yet

2 participants