Just make the line in `.gitignore` as specific as you want it to be:

    ledgerware/static/*

**EDIT 2**: TL;DR: **the answer was yes in 2013, but this flaw has been fixed**

By following the Getting Started instructions on vagrantup.com, I seem to end up with a virtual machine that is accepting SSH connections on port 2222 so that anyone can get root access to my VM and read my host working directory using the default credentials (username=password=vagrant or vagrant_insecure_private_key).

Is this true? If yes, why is it not considered a gaping security vulnerability? What if I had copied sensitive data to the VM?

**EDIT**: and for those who think anyone on the internet being able to read your sources and executing arbitrary code on your VM is not that bad, I recommend reading the &quot;Breaking out&quot; section in this blog post http://blog.ontoillogical.com/blog/2012/10/31/breaking-in-and-out-of-vagrant/

In a nutshell: running Vagrant &quot;as intended&quot; can also enable anyone to break into your host/development machine (e.g., by using a malicious git post-commit hook).



Vagrant insecure by default?

While JavaScript&#39;s type-strict comparison operators (`===`, `!==`) are nice, it doesn&#39;t have corresponding strict comparisons for greater/less than.

    var x = 10;

    x &lt;= 20;    // true
    x &lt;= &#39;20&#39;;    // true
    x &lt;== 20;   // true (or would be, if JS had such an operator)
    x &lt;== &#39;20&#39;; // false (ditto)

Why not?  I ask this question fully expecting the answer to be &quot;uh, because it doesn&#39;t&quot;, but I&#39;m asking anyway, in case there&#39;s an interesting and/or disheartening historical reason for such operators being omitted.

Why doesn&#39;t JavaScript have strict greater/less than comparison operators?

&gt; **Possible Duplicate:**  
&gt; [Ignoring directories in Git repos on Windows](https://stackoverflow.com/questions/343646/ignoring-directories-in-git-repos-on-windows)  

&lt;!-- End of automatically inserted text --&gt;

My web app has the following directory layout:

    myapp/
        .gitignore
        .git/
            ...

        static/
                mytest.txt
                fgs.ico
        ledgerware/
            static/
                mytest.txt
                fgs.ico
            ...


I&#39;d like to edit existing myapp/.gitignore file so that when git push it ignores all files inside myapp/ledgerware/static folder, but NOT myapp/static folder. Can someone help me with this?


.gitignore a folder content

> Possible Duplicate: 
> <a href="https://stackoverflow.com/questions/343646/ignoring-directories-in-git-repos-on-windows" target="_blank" rel="noopener noreferrer">Ignoring directories in Git repos on Windows</a>

My web app has the following directory layout:
<pre><code class="hljs language-arduino">myapp/
 .gitignore
 .git/
 ...

 static/
 mytest.txt
 fgs.ico
 ledgerware/
 static/
 mytest.txt
 fgs.ico
 ...
</code></pre>
I'd like to edit existing myapp/.gitignore file so that when git push it ignores all files inside myapp/ledgerware/static folder, but NOT myapp/static folder. Can someone help me with this?

I&#39;m thinking if there is a way that when I merge a branch into another branch that ALL changed files are listed in my commit message and not just the ones which were modified in both branches.
This would give me a better overview of what was changed in the branch just by seeing the merge commit.
Is there a way to do this?

List all modified files in git merge commit - even the fast forwarded

Please, I have a big problem in my project: this is the scenario.
I have an xcode project under GIT. Today I realized that the last commit broke some tests, so i checked out the previous commit.
I used SourceTree and this is the warning

&gt; Doing so will make your working copy a &#39;detached HEAD&#39;, which means you won&#39;t be on a branch anymore. If you want to commit after this you&#39;ll probably want to either checkout a branch again, or create a new branch. Is this ok?

I worked for an entire day and at the end I committed everything.
So I needed to merge my work on develop branch so I checkout the develop branch and...my work instantly disappeared :(

I know it was wrong to detach my HEAD and Sourcetree warned me...but there is a way to restore my work?


GIT restore last detached HEAD

Is there a way I can stash just my staged changes? The scenario I&#39;m having issues with is when I&#39;ve worked on several bugs at a given time, and have several unstaged changes. I&#39;d like to be able to stage these files individually, create my .patch files, and stash them away until the code is approved. This way, when it&#39;s approved I can stash my entire (current) session, pop that bug and push the code.

Am I going about this the wrong way? Am I misunderstanding how git can work in other ways to simplify my process?

How can I stash only staged changes in Git?

Suppose I pull changes from a git repo. Then the author of the repo force pushes to the central repo. Now I can&#39;t pull since the history is rewritten.

How can I pull the new commits (and abandon the old ones), assuming that the author force-pushed the correct version?

I know this is bad git workflow, but sometimes you can&#39;t avoid this.

How to pull after a forced git push?

I&#39;m curious why GitHub calls submissions to merge, &quot;Pull requests.&quot;

From my understanding, `git pull` will pull all changes, from a remote repository, into a current working branch.  Then merge those changes with `FETCH_HEAD`. ([Git Pull][1])

So taking a look at `git push`... a push would actually push committed changes to a repository.  And isn&#39;t that what you are doing with a Git repo?  Submitting a &quot;request&quot; to merge your code? So why isn&#39;t it called a &quot;Push request&quot;?

  [1]: http://www.kernel.org/pub/software/scm/git/docs/git-pull.html

Why does GitHub call foreign submissions, a &quot;Pull Request&quot;?

Title says it all. I am trying to add my NuGet packages to the repository. Everything but the .dll files are being detected. 

The gitignore file contains no references to *.dll. The .dll files don&#39;t get recognized when located anywhere in the entire repository. info/exclude is also empty.

I have also cloned the repository (file-system to file-system as opposed from remote to file-sysytem) with no luck. This issue also happens on two different computers.

I could add the .dll files manually, but they should be tracked. Why are they not being tracked?

git repository ignoring all .dlls

`.gitignore` can ignore whole files, but is there a way to ignore specific lines of code while coding?

I frequently and repeatedly add the same debug lines in a project, only to have to remember to remove them before committing. I&#39;d like to just keep the lines in the code and have git disregard them.

How to tell git to ignore individual lines, i.e. gitignore for specific lines of code

I&#39;m trying to avoid the following pattern in my `.gitignore` file.

    MyPrject/WebApp/Scripts/special/*.js
    MyPrject/WebApp/Scripts/special/*/*.js
    MyPrject/WebApp/Scripts/special/*/*/*.js
    MyPrject/WebApp/Scripts/special/*/*/*/*.js
    MyPrject/WebApp/Scripts/special/*/*/*/*/*.js
    MyPrject/WebApp/Scripts/special/*/*/*/*/*/*.js
    MyPrject/WebApp/Scripts/special/*/*/*/*/*/*/*.js

We tried:

    MyPrject/WebApp/Scripts/special/**.js
    MyPrject/WebApp/Scripts/special/**/*.js

This however didn&#39;t work. This is git on Windows. Is there a more concise way to do this without repeating things?



How to .gitignore files recursively

I have a file in a git repository that has a local change on it. I want to have git ignore the local change forever, but not the file. In particular,

  - If the file isn&#39;t touched besides this change, `git add .` should never stage it.
  - Likewise, `git commit -a` shouldn&#39;t commit it.
  - If I ever make an additional change to the file, I should be able to stage and commit that change - but the change I&#39;m ignoring should *not* be staged and committed.

Is there a way to do this? Doing some research, I read about &quot;smudge/clean cycles,&quot; where, if I read correctly,

  1. the file would be marked as unchanged,
  2. the change I made would be overwritten when I checkout,
  3. and then a script would automatically reapply the change and then mark the file as unchanged again.

I am very new to git and scripting, though (I&#39;m an intern with C# and Java experience), so if that&#39;s what I need to do, can you please post detailed directions or a link to a tutorial on how to set a smudge/clean cycle up?

**Background:** I want my working branch to be out of sync with the trunk. There is a low priority bug that only affects development machines, so rather than fix it, we&#39;re just commenting out the offending code. Obviously, we don&#39;t want this code to be removed from production, where it works just fine.

Content Type	Original Author	Original Content on Stackoverflow
Question	synergetic	View Question on Stackoverflow
Solution 1 - Git	FoolishSeth	View Answer on Stackoverflow

.gitignore a folder content

Git Problem Overview

Git Solutions

Solution 1 - Git

Why doesn't JavaScript have strict greater/less than comparison operators?

Vagrant insecure by default?

Attributions