gitignore

Xcode 7: ignore .xcscmblueprint in repository?

笑着哭i 提交于 2019-12-03 07:20:55
问题 I noticed that Xcode 7 creates a new .xcscmblueprint file in the xcshareddata folder. Will it be always auto generated? Should this file be added to the ignore list of the repository, or should it be checked in into repository? Xcode 6 has the .xccheckout file, I've always gitignore'd that file. 回答1: I'm gitignoring them, for exactly the same reason as .xccheckout. GitHub's maintained .gitignore added that too, for both Objective-C and Swift. https://github.com/github/gitignore 回答2: I think

Recursively include Nuget DLLs via Gitignore

此生再无相见时 提交于 2019-12-03 07:08:44
I am using GIT with a new ASP.NET MVC project. I have a line in my gitignore file to ignore dlls *.dll I would like to add something along the lines of the following to include (i.e. do not ignore) DLLs in my NUGET packages folder !/packages/*.dll The problem I'm encountering is that not all nuget packages are created equally and, depending on the package in question, DLLs may be nested an arbitrary number of levels in the path hierarchy. It seems that I simply need a recursive solution along the lines of: !/packages/**/*.dll !/packages/**/* I have not yet found a solution that will work via

How to ignore a file which is already committed?

情到浓时终转凉″ 提交于 2019-12-03 06:41:58
问题 Previously, the following was my .gitignore file: ... config/database.yml .DS_Store Later I created an app_config.yml file in the config directory and committed it. Now, I realized that I don't need the app_config.yml file in the git repository. And I modified my .gitignore file: ... config/app_config.yml config/database.yml .DS_Store Now, when I commit, that app_config.yml file is still in my repo. I want to remove that file from my repo. How can I do it? 回答1: As mentionned in "ignoring

How to I add something to the .gitignore so that the match is not recursive?

徘徊边缘 提交于 2019-12-03 06:27:55
问题 How to I add something to the .gitignore so that the match is not recursive? For example, I wish to ignore the directory foo and the file bar.txt in the current directory, but not any that exist in subdirectories. I have tried this for my .gitignore file: foo/ bar.txt But unfortunately git applies this recursively, so that otherdir/bar.txt and otherdir/foo/ also get ignored, which is not what I want. (Is there a command in git that shows me all ignored files, and reference the .gitignore file

Meaning of leading slash in `.gitignore` file

落爺英雄遲暮 提交于 2019-12-03 06:25:19
问题 If I put a pattern in a .gitignore file with a leading slash, does the slash refer to the directory in which the .gitignore file is located, or does it refer to the root of the whole repository? (The man pages I have found have hidden this information carefully.) 回答1: This is the documentation text: A leading slash matches the beginning of the pathname. For example, "/*.c" matches "cat-file.c" but not "mozilla-sha1/sha1.c". These are my guesses: If you use an in-repository- .gitignore , the

Ideal Android Studio gitignore file

安稳与你 提交于 2019-12-03 05:55:12
问题 i recently created an Android project but it is my first time to work with Android Studio, i placed the project in a Git folder to be able work with another developer remotely through Git and i found that the default .gitignore file contains the following: *.iml .gradle /local.properties /.idea/workspace.xml /.idea/libraries .DS_Store /build /captures i just wondering is this the ideal gitignore file to be able work together remotely? or i have to edit or remove some files from it?! 回答1: As

.gitignore regex for emacs temporary files

寵の児 提交于 2019-12-03 05:53:09
I'm trying to .gitignore emacs temporary/autosave files. I'm using... \.\#.* in my .gitignore. But git add -A run in a subfolder is still giving me: # new file: .#make_collections.py # new file: .#norm_collections.py # new file: make_collections.py # new file: norm_collections.py even though \.\#.* is clearly getting the right file names and not the wrong ones when I test it with a regex tester . You can also instruct emacs to save the autosave files in a different directory altogether by setting the variable auto-save-file-name-transforms , I have this in my init file (setq auto-save-file

Should the package-lock.json file be added to .gitignore? [duplicate]

拈花ヽ惹草 提交于 2019-12-03 04:50:43
问题 This question already has answers here : Do I commit the package-lock.json file created by npm 5? (10 answers) Closed last year . To lock the versions of dependencies that are installed over a project, the command npm install creates a file called package-lock.json . This was made since Node.js v8.0.0 and npm v5.0.0, as several of you might know. Despite of Node.js and npm recommendations about committing this file, several concerns regarding when you should avoid to do it, are also an option

Is it a good idea to put db/schema.rb to .gitignore list ?? [closed]

做~自己de王妃 提交于 2019-12-03 04:41:51
Closed . This question is opinion-based. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . so what I'm suggesting in my job, is to put db/schema.rb into .gitignore file, so we don't have (time to time) merging problems. There are some concerns that if something terrible happen (meteor fall from the sky right on the DB server and simultaneously all the db/migrete files are corrupt) we could loose the schema, and we will have to use rake db:purge (to reuse the schema.rb). I

Tell Sublime Text to ignore everything in .gitignore?

送分小仙女□ 提交于 2019-12-03 04:41:17
问题 Vim has this great plugin to convert the current project's .gitignore into a syntax understandable by Vim and from there exclude all those files from opening. Using Sublime Text 3's 'Go to Anything' (CMD+P), I get lots of files I'm not interested in, such as stuff under .build and .meteor . Is there something similar for ST3? 回答1: I created a quick-and-dirty plugin, sublime-gitignorer, to solve exactly this problem. It is currently tested on Ubuntu and Windows in Sublime Text 2 and 3. I